The title is a half-joke I've started using to describe Orven. When someone asks me what Orven is, it's the one-line answer I give them.
Orven lets you close all your other windows. You won't need them.
The longer answer is that Orven comes from a frustration I've had for years with the promise that AI will make you 1000x more productive if you just embrace it. If it isn't working for you, you're holding it wrong. You just have to embrace it. Why won't you embrace it?
I have embraced it. I use AI every day and I like it. Where I keep getting stuck is the tooling around it. So much of what gets built is sandcastles, and cute little shovels for building more cute little sandcastles. There's enough of it now that "demoporn" has become a word people use. I've been on the internet for 25 years, 20 of them working as an engineer, and until recently I'd heard that word maybe once or twice. Now I hear it every day.
A lot of AI tooling never gets past the demo stage. Building elaborate sandcastles with nicely decorated shovels is fun, but in my day-to-day work AI has mostly either given me more work or made the work worse.
I got tired of waiting for the tools I'd been promised, so I started building one. Orven is a single workspace that holds everything relevant to the work you're doing.
Your editor is in there. I use Neovim, and Orven also integrates with other terminal editors. Your agents are connected to the editor, and your debugger is connected to both, so you and the agents can use the same one. Your database, your web server and your documentation are in there too. Orven is built on plugins, so anything else you want close at hand can go in as well. Orven itself provides the interface and the layer underneath that lets all of these pieces talk to each other and share information, including anything you build on top.
Want your Linear or Jira tickets next to your agents? That's easy. Want to keep an eye on your CI pipeline while you work on one feature and an agent tests another in the background? That works too. You can also connect Orven to your production server and watch the logs. When an error comes in, it goes to an agent, which checks out the code on your dev server, starts a debugger and drives it until it isolates the problem, then puts up a fix as a PR.
Once a workflow like that is set up, you can run it again whenever you need it, and it becomes part of how your day works. I built Orven to fit the way I work, and the plugin system is there so you can make it fit the way you work.
If that sounds useful, give Orven a try.