Discussion

Orchestrate your AI coding agents

toastal: > FeaturesIt’s blank. Lots of blank gray rectangles too. Site is broken?

sausajez: Please review the site design. Between the thin blue lines appearing & disappearing, and the "television static" in the background I gave up attempting to read anything in the first 30 seconds on the site because my eyes were drawn anywhere other than the content.

throwaw12: This looks impressive!How do you restore the state from the old workspaces? do you spawn tmux and resume the conversation or do you do it differently? from the video it felt like instant

tordrt: The underlying git worktree still lives on your disk until you delete it. So its not harder than starting a terminal with claude --continue, or codex resume --last inside the git worktree, depending on what agent the user used.

Renaud: Nice tool for working multiple sessions without them tripping over each-other.I appreciate that you provided multiple OS versions rather than just go for Mac only like some.

saberience: Nice work! Congrats on the release, did you check out Vibe-Kanban or Emdash which are both building in this space?https://www.emdash.sh/https://vibekanban.com/What is your secret sauce, so to speak? I personally built my own local tools and system for this, I tried vibekanban but didn't feel like it added much to my productivity, haven't tried emdash yet.

zephyrwhimsy: The observability stack (logs, metrics, traces) is often an afterthought but should be a first-class architectural concern. You cannot improve what you cannot measure, and you cannot debug what you cannot observe.

zephyrwhimsy: I have seen teams spend months fine-tuning retrieval algorithms when the real issue was that their ingestion pipeline was feeding HTML boilerplate into the vector store. Fix the input first.

riskable: How can people afford to use Claude Code like this‽ Is everyone just playing with it on their employer's dime or what?

zephyrwhimsy: Markdown as an intermediate format for LLM pipelines is underappreciated. It strips noise while preserving structure.

electrovir: VC funding + spending more money on Claude instead of hiring more engineers

electrovir: I've built my own as well, in a terminal. Not pretty, but does the job until something better comes along (maybe Baton is that something better): https://github.com/electrovir/agent-storm

ismail: I have not done much multi-agent development. Trying to understand what problem this solves, surely one can spin up multiple terminal tabs?

techgnosis: This uses the CLIs so its using subscription pricing, not token pricing

michaelbuckbee: I build my own products and services and the effective ROI for paying for a more or less unlimited max Claude Code plan is fairly ridiculously positive.

Bombthecat: Like you make money with them?

causal: I'm confused, I've been running parallel agents on different worktrees within a single view of Claude Desktop for at least a month. I don't see any new features here?

mellosouls: Best of luck with this but I think with so many open source agent managers cropping up, you are going to need to provide very special USP to have people choose yours over the free and open versions.I guess I would suggest that should be a priority for your site and documentation, to help devs understand what that value offer is.Your site does seem nicely presented though and clarity in capability is possibly an early win over some of the more chaotic documentation elsewhere.

ale: I don’t know how to phrase this without sounding like an arrogant idiot but seriously: what are people actually programming with agents + worktrees + harnesses + tasks + skills + whatnot? Most workflows I see people adopt involve large amounts of infrastructural fluff only to (more) quickly generate what I (anecdotally) have seen is somewhere between code generation of boilerplatish React/laravel/your-fav-framework components for web or native, and niche toy apps for mostly personal use. My very limited usage of agents has been for scanning large (bloated) codebases to get rid of unused code, meaning time consuming and tedious tasks. But it seems the general trend is that programmers just want faster horses?

sam0x17: Yeah perfect example, the main thing I _would_ use multiple agents on is optimizing/benchmarking code, but for that you specifically can't use worktree, you need one agent per machine or they'll taint each other's benchmarks