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.<p>I guess I would suggest that should be a priority for your site and documentation, to help devs understand what that value offer is.<p>Your site does seem nicely presented though and clarity in capability is possibly an early win over some of the more chaotic documentation elsewhere.
I started building a similar project for myself, a terminal PTY running through a desktop daemon: <a href="https://youtu.be/6KY-HCn3SaA" rel="nofollow">https://youtu.be/6KY-HCn3SaA</a><p>The fun part being it worked on mobile too: <a href="https://youtube.com/shorts/CmemwDGwpx8?si=xzAJBb8ha7DLIDmY" rel="nofollow">https://youtube.com/shorts/CmemwDGwpx8?si=xzAJBb8ha7DLIDmY</a><p>It was more of a tool for myself but some interest from others inspired me so iterating on it. People interested in this kind of thing should join my slack! <a href="https://monetworkspace.com/terminal" rel="nofollow">https://monetworkspace.com/terminal</a>
How can people afford to use Claude Code like this‽ Is everyone just playing with it on their employer's dime or what?
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.
This uses the CLIs so its using subscription pricing, not token pricing
VC funding + spending more money on Claude instead of hiring more engineers
200 dollars a month goes a long way with claude code
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.
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?
Very cool. And congrats on the launch.<p>I started to use superset 2 days ago. Which seems similar. It's pretty nice: <a href="https://superset.sh">https://superset.sh</a><p>Fyi: here are some things I would like to have for such a tool
- notification when an agent is done
- each tabs/space has its own terminal, browser, agent
- each tab/space runs in a sandbox (eg docker)
- each tab/space can run my dev server. But must not conflict with the other dev servers running
- each tab/space has a mcp server for the built in browser<p>Nice to have:
- remote access against my machine/tabs
- being able to make screenshots
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.
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?
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
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): <a href="https://github.com/electrovir/agent-storm" rel="nofollow">https://github.com/electrovir/agent-storm</a>
Nice tool for working multiple sessions without them tripping over each-other.<p>I appreciate that you provided multiple OS versions rather than just go for Mac only like some.
I have tried to provide after best ability, but have only been testing them on vm's on my mac! So be aware. I labeled them Beta due to this. But most features should work fine, probably better on linux than windows.
This looks impressive!<p>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
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.
This looks great. How do you compare to cmux?
Congrats on your launch! How is this different than Conductor?
The main difference is that Baton is agent-agnostic and terminal-native. It doesn't add a GUI on top of Claude Code or Codex, it builds around the terminal itself, so you run whatever agent CLI you want natively, but with convenient shortcuts for launching them. Which is a nicer experience in my view, but people have different views on this.<p>Baton is also more git-aware. Instead of just showing raw diff line counts, you see commits ahead and behind your target branch, so you can tell at a glance how far each workspace has diverged and shortcuts for resolving it in the matter you want.<p>One thing I think is unique is the built-in MCP server. It lets agents spawn new workspaces programmatically, so you use an agent to launch agents in new isolated workspaces.
Would be curious if it is more polished than Conductor. Memory leaks and random bugs seem to crop up in Conductor far too often.
If nothing else, I see that Conductor is currently Mac only.
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.
Are agents at worktree level or can a single agent and chat work on a parent directory above multiple worktrees of different repos?
> Features<p>It’s blank. Lots of blank gray rectangles too. Site is broken?
I have not done much multi-agent development. Trying to understand what problem this solves, surely one can spin up multiple terminal tabs?
Nice work! Congrats on the release, did you check out Vibe-Kanban or Emdash which are both building in this space?<p><a href="https://www.emdash.sh/">https://www.emdash.sh/</a><p><a href="https://vibekanban.com/">https://vibekanban.com/</a><p>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.
Go away, I'm baitin'!
[dead]
[dead]
[flagged]