Wanted to share this dependency hell post mortem, to remind everyone it's never easy to fully be safe from global outages, and if you want to be fail proof you really need to mind your dependencies and failure points on top of self-hosting a lot...
That's very cool! I actually built a Claude Code Web alternative* over the last few months and made my own auto-commit solution for it. I reckon though having the prompt is what helps me and the agent generate relevant prompt messages that can explain the why.
Anyway even a average commit message is way better than none
Yeah that's why we basically built our own Claude Code Web but around Hetzner VPSs instead & terminal access. So you can use docker, open ports if you'd like. Some teams even needed us for a complicated R dev setup they wanted Claude to work with.
It means they better fill a niche. We ourselves built our own twist on cc web and we found differentiation that they couldn't. For instance running claude in real VPSs in which you can run docker & docker compose, connect to via SSH or even host stuff. We also made our own file sync so you start on web, continue on desktop in your IDE, run code locally, go back to web & mobile...
I think IDEs we're gonna see Vims, Emacs, Jetbrains, Vscode. For now CC web seems to be the sublime text of that world, and Terragon/Sculptor are yet to differentiate enough like a jetbrains
We try to be the jetbrains of this, which is not a smart move for a bigger co like Anthropic to take
We're two european builders who spent the last 2 months building Ariana, essentially Claude Code Web on steroids with some aspects ressembling Conductor.
We were frustrated with how managing multiple coding agents, sync and async, was feeling. Always either too much friction to go all-in most times, and once all-in too hard to manage. Especially as a team.
In Ariana you can launch multiple agents powered by your Claude Code on the same codebase, they go on to work on their own Hetzner VPS, on their own branch. They auto-commit, and you can generate a PR in the end.
You can launch & use agents from web, mobile web, desktop (win, mac, linux).
Why VMs over local git worktree? Well it doesn't clutter your disk space. It also makes agents shareable (one link share with your team), and useable from anywhere even away from the desktop. For example, you can start an agent on your local code and keep prompting it later in the metro.
Coding in a cloud VM is often annoying because you'd like to run or edit the code locally in your IDE. So on desktop we added real-time bidirectional file sync and network forwarding which allows you to fully focus on one agent as if it was there locally while the others keep working. You can also fork agents and by switching focus test multiple variants or features.
VMs can run anything like docker, docker compose, most languages. They each have an IP with firewall on by default. You can open ports and host what your agent worked on even.
We leave it for you to discover many other features and quality of life UX things.
You can try it on the web immediately for free using you claude subscription or API key. Linking a GitHub acc is optional (can just give a public clone url from github, gitlab, azure or bitbucket), but usage is more limited.