Looking at the screenshots, this looks close to what an agent factory for teams could look.
Agents on multiple servers, people can see each conversation. Test it…
I sometimes use 5 agents at once, but 3 work on separate tasks and the 4th is watching them by tmux and steering, and the fifth is also watching the whole team for testing quality standards. So 2 out of five are just helping me watch the other 3.
But this only works because the 3 worker agents have really separate problems, almost no connections across.
an ide built around agents instead of files is the direction i keep expecting to win. how do you handle state when several agents touch the same repo at once
Worktrees or sandboxes. You can tell Claude to put its stuff in a worktree. I can easily develop any amount of features in the same codebase because they all run in their own worktree
I went from IDE (VS Code) to terminal (wezterm) running half a dozen agents in an app called Herdr. My computer work is mostly in the terminal now, prompting agents. And they have access to my Obsidian vaults. Can read, and add to them. And access all my notes via a local RAG. I neither need projects in Claude, nor IDEs. Just agents accessing my local vaults and code repos.
I dont care about codex,cc harness. but I do miss a proper terminal in pi web; I will likely endup forking it... the lamma cpp built-in web app is super nice, but also needs to be hacked to support api providers, and also no terminal :/ .
I think the definitive solution way would be using vscode stripped for web (what gh codespaces use) and add pi to it.
32 comments
[ 0.19 ms ] story [ 4.3 ms ] threadBuilt in containerization and EC2 support, allows moving sessions across harnesses/profiles/machines
But this only works because the 3 worker agents have really separate problems, almost no connections across.
- what makes this one special?
I think the definitive solution way would be using vscode stripped for web (what gh codespaces use) and add pi to it.