The multi-thread, worktree-based interface will probably look familiar. The parts HN may care more about are the containerized workspaces, remote-host model, and local merge queue for multi-agent work.
Interesting, one challenge with other ADEs (nice term btw) like Conductor is that code navigation is terrible and too much emphasis is on a GUI for Claude.
We really need the best of both worlds: IDE (powerful like Intellij) + ADE (multitasking code)
And how does it compare to other tools like Conductor?
Very nice. Does this support GitHub Copilot subscriptions (oauth/hmac) or do you have plans for it? That would make or break for me because of the API costs.
Similarly I built a self-host able replit-like server with RAG but it's more end-user focused than developer focused...
Does this solve indexing of codebases like Cursor does, or do you still need tools / plugins like Lumen (https://github.com/ory/lumen) for that in order to work in larger codebases without wasting tens of thousands of tokens on tool calls and brute force guessing with grep?
Looks cool! Two things: I see you mentioned the merge queue, but how exactly do people avoid or resolve merge conflicts when merging work from two or more agents in the separate worktrees? I havent really seen a seamless way to approach this or do people just have the agents work on distinctly unrelated stuff? Secondly, are containers the primary sandboxing appraoch? or do you support vms?
Fundamentally one of my biggest gripes with tools like this is that often you are not working with a single repo in anything beyond simple apps.
When I am working with Claude I am often doing it from the root directory of a workspace of dozens of repos. I work with Claude to come up with a plan for implementing a feature and it investigates and plans.That plan often encompasses multiple repositories. Claude then turns large scale plans into smaller issues, or tickets as artifacts.
conductor was a non-starter for due to requiring the github + PR workflow. do you just allow management of a local repo without pushing us into a specific git flow? worktrees for diff work is fine, just if you want to handle the merge yourself (for whatever reason) how would that work.
It's not open source, but is it free? I'm assuming you have plans on making money off of it somehow, can you share anything about what that will look like?
The challenge every tool in this space faces is the same: how do you give the agent enough autonomy to be useful without losing the ability to course-correct when it drifts? Interested in how ctx handles the context window boundary.
21 comments
[ 2.6 ms ] story [ 37.5 ms ] threadThe multi-thread, worktree-based interface will probably look familiar. The parts HN may care more about are the containerized workspaces, remote-host model, and local merge queue for multi-agent work.
We really need the best of both worlds: IDE (powerful like Intellij) + ADE (multitasking code)
And how does it compare to other tools like Conductor?
Similarly I built a self-host able replit-like server with RAG but it's more end-user focused than developer focused...
https://github.com/ctxrs/ctx
https://ctx.rs/ade-vs-ide
TLDR: use an ADE if you need multiple agents working concurrently on your code base. Otherwise IDE with an agent plugin is probably fine.
When I am working with Claude I am often doing it from the root directory of a workspace of dozens of repos. I work with Claude to come up with a plan for implementing a feature and it investigates and plans.That plan often encompasses multiple repositories. Claude then turns large scale plans into smaller issues, or tickets as artifacts.
- "I tried 47 agentic AI cli tools posted on HN in the last month. Here are the shocking results"
[0] https://github.com/ctxrs/ctx