Show HN: Agentastic.dev is Ghostty and Git worktrees = multi-agent CC/Codex IDE (agentastic.dev)

11 points by ahmadyan ↗ HN
I’ve been tinkering with what a “multi-agent IDE” should look like if your day-to-day workflow is mostly in terminal (Claude Code, OpenAI Codex, etc.). The more I played with it, the more it collapsed into three fundamentals:

* A good TUI: Terminal is the center stage, with other stuff (CodeEdit, Diff, Review) baked on the side. I don’t like piping Agent’s output through some electron wrapper, here you get to run CC/Codex/Droid/Amp/etc directly.

* Isolation: agents shouldn’t step on each other’s toes. The simplest primitive I’ve found is Git worktrees. It is not as isolated nor heavy as containers/vms, but it is the next best thing for working locally. Each agent gets its own working directory and their own snapshot of the repo. Git worktree requires CLI kung-fu, but agentastic simplifies it through some nice GUI and keyboard shortcuts for easy creation/switching/etc.

* An excellent terminal: I couldn’t get comfortable with xterm.js (Code/Cursor/Conductor/etc), and i loved Ghostty, it is fast, pretty, and feels right. So naturally the whole experience is built around Ghostty (There is also SwiftTerm as an alternative option).

Agentastic.dev is a native mac IDE, built around the workflow of “one task = one worktree = one terminal session” as the default. You spin up multiple worktrees (branches) and run different agents in parallel, each with its own clean working directory and terminal session and codeedit, then review and merge when you’re ready.

We’ve been dogfooding it to build http://agentastic.dev itself and agentastic.com (coming soon), and it’s noticeably improved our productivity. https://pasteboard.co/xg1YOsk5MIn9.png

It’s early and still rough in places. I’d love feedback from people who use worktrees heavily or run multiple coding agents:

- What would you want from a multi-agent IDE that you can’t get from a terminal + tmux?

- What’s missing / annoying in your current worktree workflow?

4 comments

[ 2.7 ms ] story [ 18.8 ms ] thread
Not dissing your work but... i can barely keep up with what a single agent is doing! Just thinking about herding five of them at a time makes me mildly nervous, haha
Every time I've seen people use Git worktrees with agents, it's incredibly wasteful. What is the use case for running parallel isolated agents? Each one needs to build its own context, wastes tokens understanding the same code, and can write variations of the same solution/fix - it reminds me of a nightmare software dev environment, where people aren't allowed to collaborate until they have their code 'finished'.
Looks fun! Does it support devcontainers and/or any form of isolation? The app's purpose seems similar to that of Branchbox.

Also the website says it runs on macOS 13+, but the app's Info.plist sets LSMinimumSystemVersion to 14.0.

> What would you want from a multi-agent IDE

I use Orbstack to run docker compose for worktree each with a distinct domain ( previously using Colima + Cloudflared for same reason ). Not that this has to be done by IDE, but not bad if that's offered.