Product Thumbnail

Anvil

Run a fleet of parallel Claude Codes

Artificial Intelligence
Maker Tools
Development

The IDE for parallel agent work. MIT licensed, farm to table, fun. With one click git worktree isolation, first class plan tracking, color coding for agent states, flexible layout arrangement, and so much more, Anvil is crafted to make developers extremely productive, minimizing context switching and maximizing agent parallelism.

Top comment

Hello Product hunt, stoked to release Anvil to the world! I built Anvil after getting tired of managing multiple claude code sessions in my terminal. I felt the pain of constantly context switching between terminal tabs and git branches, forgetting which agent did what, agents bumping into each other on the same branch, not knowing when an agent was done or needing input etc... Anvil solves the annoyances of parallel agent work, so you can cook on new things while your agents run. Agent lifecycle, isolation, planning and coordination, context heigene is all handled by the IDE. But more than this, the goal Anvil is to push the frontier of what is possible with agent programming. I hope you get a chance to try out Anvil, let me know if you have any feedback, and please join the Discord. Lets cook some GPUs together 🔥

Comment highlights

As someone who's wrestled with the chaos of parallel coding, I’m curious how do you ensure effective collaboration between agents without conflicts in shared file states?

I've been running 3-4 Claude Code sessions in tmux and losing track of which agent is doing what is a daily struggle. The git worktree isolation alone would save me from merge conflict hell. Does Anvil handle cross-agent dependency — e.g., Agent B waits for Agent A's PR before starting?

How are you handling state isolation between parallel agents? When you run multiple Claude Codes on the same codebase, conflicts in shared files are the main issue I've hit. Do they each get their own branch or working copy?

this looks super fun, congrats! the REPL thing where Claude can call other Claudes programmatically sounds wild, any examples of what people are actually using that for?

Looking ahead, do you think the long-term win is (a) better orchestration/coordination (plans, dependencies, conflict avoidance) or (b) better verification (tests, linters, review agents) so humans can supervise more agents with less attention—and what did you prioritize first inside Anvil and why?

Is this forked from the VS Code as I am getting kinda similar vibe here. But the feature is really helpful considering running multiple claudes at a time and managing outputs becomes bit overwhelming.

Feels like dev tools are moving from “AI assistant”

to “AI team”.

Parallel agents sounds powerful

but also messy if not managed well.

Curious how you keep control over multiple agents working at once.