I doubt something like this can be implemented easily in a single environment without running into client and server port issues, etc.
14 karma · joined October 19, 2025
I doubt something like this can be implemented easily in a single environment without running into client and server port issues, etc.
My suggestion would be to keep things simple, pragmatic, and save development time. While git worktrees are not perfect, and they require extra space, it is easier for people to understand and easily locate this kind of structure while also being able to execute commands in a somewhat isolated environment. I would be happy if the app simply automates this for me and creates a new worktree, branch, and agent at that location as soon as I click 'Add agent'.
Then the only issues become merge conflicts between different branches... this is where extra dev time could be allocated, and implement agents that automatically merge branches.
The biggest issue I have is that it is a bit weird putting our startup ideas into someone else server. Is this open-source so we can self host? The central db for questions could still be curated by you in the repo, we would just pull to update the questions on our end. For new questions we would make PRs. You still decide which questions are good.