Agentastic.dev is Ghostty and Git worktrees = multi-agent CC/Codex IDE
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…
Agentastic.dev is Ghostty and Git worktrees = multi-agent CC/Codex IDE launched on January 5, 2026 with 11 votes, #956 of 14,585 launches that month and more than 90% of that year's launches.
In plain words
Agentastic.dev is a terminal-based IDE designed for developers working with AI coding agents like Claude Code and OpenAI Codex. It places the terminal at the center with integrated code editing, diff viewing, and review tools alongside. The tool uses Git worktrees to isolate multiple agents, giving each its own working directory and repository snapshot to prevent conflicts. Developers can run agents directly without electron wrappers and manage worktrees through a simplified GUI and keyboard shortcuts instead of CLI commands.
written from the facts on this page · September 2026
From the sources
Run Claude Code, Codex, Gemini, Cursor, Copilot, and 47+ more agent integrations in parallel — each in an isolated git worktree with diff and code review built in. Native macOS, not another Electron IDE.
Agentastic.dev is the first ADE for Human-Agent collaboration: code isolation parallel worktrees Container support Agent Agnostic terminal-first browser-use code-review persistent remote SSH Cloud Agent code isolation, parallel worktrees, Container support, Agent Agnostic, terminal-first, browser-use, code-review, persistent remote SSH, Cloud Agent Code, terminals, git, a browser, and 52 AI-agent integrations — together in a single native macOS workspace. Agentastic.dev is agent-agnostic and ships 52 built-in agent definitions. Run each one in a real terminal, or as a structured chat — 24 of them speak it natively or over ACP. Each agent works in its own git worktree or container — both…from agentastic.dev
In the maker’s words, at launch
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…
Does a similar job
all alternatives →
Parallel CodeMar 2026 · parallelcode.app · ▲159I kept running into a structural problem with AI coding tools. You try one agent. It makes changes. You try another. Now you're manually diffing branches and cleaning up experimental commits. The tools are powerful, but the workflow isn’t designed for comparison. So I built Parallel Code. It runs Claude Code, Codex, and Gemini CLI natively (no API wrapper, no feature abstraction), but isolates each agent in: its own terminal its own Git worktree its own feature branch The workflow becomes: Spawn N worktrees Assign one AI agent per worktree Let them implement independently Compare diffs Merge…
Git for AI AgentsMay 2026 · github.com · ▲129hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
Boxes.devJun 2026 · boxes.dev · ▲112Hi HN, we’re Nick and Drew, and we’re building boxes.dev – the first cloud-only agentic dev environment (ADE) that gives every Codex and Claude Code agent its own cloud computer. We’re two engineers who previously built Gem (co-founder/CTO and first hire), and we spent the last year coding almost exclusively using Codex and Claude Code. It’s been a huge change to how we code, and it’s been exhilarating seeing the models keep getting better – but we eventually realized that developing on localhost was holding us back: - Git worktrees are clunky to set up and use for parallelizing work -…
GitAgent by LyzrMar 2026 · gitagent.sh · ▲231Hey HN, We built GitAgent — a git-native, framework-agnostic open standard for defining AI agents. The idea is simple: your repo IS the agent. npx @open-gitagent/gitagent@latest run -r https://github.com/shreyas-lyzr/architect -a claude That one command clones the repo, reads agent.yaml + SOUL.md + skills/, and launches it with Claude Code. Switch `-a openai` or `-a lyzr` to run the same agent on a different framework. No code changes. Goal: is keep the gitagent as a open standard ledger for an AI Agent in a VM, with versioned memories, skills etc. An agent is…
ReplicasJun 2026 · replicas.dev · ▲239Hey HN! I'm Connor, creator of Replicas. I'm a heavy Codex/Claude Code user, and I wanted to hand off tasks to agents like I would to an engineer - kick something off before work, let it scaffold while I'm at lunch, even come back to a ready PR. The problem: existing alternatives use workspace VMs that are black boxes. I have no access to any of them - they can't run tests, read logs, or use tools like the Playwright MCP (which I use to verify agents actually fixed what they claim to fix). Replicas gives agents real cloud workspaces where they can: - Run your test suite and read the…
AgentGridJul 2026 · agentgrid.sh · ▲77Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our many projects. Our approach was to use an infinite canvas desktop app for the TUIs we already know and love, mainly claude + codex. We drew inspiration from Figma and Railway. Overtime we added image nodes, notes, terminals, coding editors, source control, etc. I wasn't sure about it at first. It took me a month to give the first version Souren built a real try. What got me was an Apple System Update I've been…
More ai this month
the category →
Paintings by AI models: programs run through a simulation of oil paint.
AI · 20d ago · stillwet.art
PixVerse R2▲381A real-time world model you can explore and change
AI · 28d ago · world.pixverse.video
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, January 2026
the whole month →- IN
Hey HN! I wanted to share something I built over the last few weeks: isometric.nyc is a massive isometric pixel art map of NYC, built with nano banana and coding agents. I didn't write a single line of code. Of course no-code doesn't mean no-engineering. This project took a lot more manual labor than I'd hoped! I wrote a deep dive on the workflow and some thoughts about the future of AI coding and creativity: http://cannoneyed.com/projects/isometric-nyc
AI · Jan 2026 · cannoneyed.com
Automatic AI-powered code reviews the moment you open a PR
Dev tools · Jan 2026 · kilo.ai
