Who builds Loupe, and why
I am Geoffrey Bachelet, and I build Loupe.
Why I built it
I was tired of watching a row of Claude Code sessions in terminal windows. The workflows wrote many Markdown files, and I could not read them well. I had no good way to mark a passage or send feedback on it. So the first version of Loupe was a document reviewer.
Then I saw that I also wanted to review the end result, not only the documents. So I added live review, where I mark the running app and the feedback goes back to the agent.
Then I saw that I still juggled terminals when I built features in parallel. So I added the board, and Loupe grew from there.
I build Loupe with Loupe, and I use it every day to build my other apps too.
How Loupe is different
- Loupe is workflow based. Rules on the board decide what work a card needs next, from product design to tech design, build, review and merge. You change the rules to fit how you work.
- Loupe does more than start agents. It is also where you review their work: the documents, the running app and the pull requests.
- Loupe has strong analytics. It records each worker run, so you can see what your agents cost, where they spend their time, and which change made them better.
How Loupe lasts
Three things keep Loupe going.
- The hosted plan is how Loupe pays for itself.
- Loupe is open source under the AGPL licence, and you can host it yourself. If I stop, the code stays usable by anyone.
- I use it every day, for Loupe and for my other apps. I need it to keep working.
Find Loupe
The code of Loupe is at github.com/loupe-ac/loupe, and Loupe posts at x.com/LoupeHQ. You can also talk to me on the Discord server.
Try Loupe
Run Loupe on your own server, or join the waitlist.