What's the advantage over just using claude --worktree? (https://code.claude.com/docs/en/common-workflows)
Show HN: ChatML - Run Claude Code Parallel Sessions in a Desktop app
11–15 of 15 posts
Re: Show HN: ChatML - Run Claude Code Parallel Sessions in a Desktop app
#12What's the advantage over just using claude --worktree? ( https://code.claude.com/docs/en/common-workflows )
claude --worktree is great for isolating a single session, but you're still juggling terminal tabs manually — starting each one, switching between them to check progress, reviewing diffs by hand.
ChatML is basically the management layer on top of that. You get a dashboard where you can run 3-5 agents at once, each in its own worktree, and see what they're all doing without tab-switching. It also handles the worktree lifecycle for you (creation, branching, cleanup), has a built-in diff viewer with code review, tracks cost per session, and lets you open PRs directly.
Closest analogy: running containers manually vs. having Compose manage them. Same underlying primitive, but the orchestration matters once you're doing it regularly.
Re: Show HN: ChatML - Run Claude Code Parallel Sessions in a Desktop app
#13What's the advantage over just using claude --worktree? ( https://code.claude.com/docs/en/common-workflows )
claude --worktree is great for isolating a single session, but you're still juggling terminal tabs manually — starting each one, switching between them to check progress, reviewing diffs by hand. ChatML is basically the management layer on top of that. You get a dashboard where you can run 3-5 agents at once, each in its own worktree, and see what they're all doing without tab-switching. It also handles the worktree…
Got it. I will try it out.
Re: Show HN: ChatML - Run Claude Code Parallel Sessions in a Desktop app
#14[dead]
Re: Show HN: ChatML - Run Claude Code Parallel Sessions in a Desktop app
#15the "containers manually vs compose" framing is exactly right -- that's the coordination layer that's missing from raw worktrees.
one thing i'm curious about with chatml: how's the experience on windows and linux? you mentioned it's running but with bugs. i built pane specifically because conductor and most of the other tools in this space were mac-first (or mac-only), and a huge chunk of the multi-agent dev community is on windows or linux.
pane is the same app, same shortcuts, same UI across all three. not "cross-platform eventually" -- ships to all three now. built on xterm.js (same engine as vs code) so terminal compatibility isn't a thing you have to debug.
if anyone on windows or linux is hitting walls with chatml or conductor, pane might be worth a look: github.com/Dcouple-Inc/Pane