Run five coding agents without them overwriting each other.
ReplicaMD gives every agent its own Git worktree, its own live terminal and its own memory, then keeps them side by side in one window. It drives the CLI you already pay for — Claude Code, Codex, Gemini, OpenCode — on your machine, against your folders.
Free. No account. Nothing leaves the machine.

Real shells, not a transcript
Each agent works in its own git worktree with a live pty. This frame shows git log, ls, and git status actually executing in the pane.
Unretouched captures of the running desktop build. No mockups or composited interfaces are used anywhere on this site.
The second agent is where it breaks.
One agent in one terminal is fine. Open a second against the same checkout and they fight over the working tree, the branch and the dev server port. So you tab between windows, lose track of which one changed what, and close the laptop knowing tomorrow starts with re-explaining the project.
Isolation is a solved problem in Git. ReplicaMD applies it to agents, and keeps the terminals alive between sessions.
A team is a folder and its members
- AI memberIts own checkout, its own memory, its own runtime. Does the work.
- BrowserA page the team keeps open - docs, a dashboard, the app you are building.
- NotesA Markdown surface over the team folder.
- TerminalA plain shell in the team folder. No AI attached.
How it works
Four steps, no ceremony.
Registry
40 plugins and 9 presets, ready to install.
Slash commands, MCP servers, skills and themes. Install them from the app, or write your own - a plugin is a folder with a manifest, and publishing it is one button.
Finds the hardcoded colours and one-off font sizes that quietly break your dark theme, and maps each one back to a token.
How to write the small text that carries an interface: empty states that teach, errors that name the way out, buttons that say what they do.
Writes the tests that would have caught the bug, in the style the project already uses.
Finds the project's real test command and runs it, then reads the failures for you.
Four terminal palettes tuned for long sessions and for telling members apart at a glance.
Turns yesterday's real git activity into a standup you can read out - no invented progress.
Who installs this
Engineers running more than one agent
You already have Claude Code or Codex open. The second one is the problem: same checkout, same branch, two sets of edits.
Tech leads on small teams
Give each member a role, a working folder and a runtime, and keep the record of what each one decided.
Contractors juggling repos
One team per client, each with its own folder, its own members and its own memory. Nothing bleeds across.
Anyone who cannot upload the code
Your repository, your notes and your provider logins stay on the machine. There is no ReplicaMD account to create.
Skip it if
- You want a chat window. ReplicaMD runs CLIs in real terminals; if you are happy in one chat tab, this is more machinery than you need.
- You want us to host it. There is no server, no sync and no web app - the desktop app is the whole product.
- You do not have an AI coding CLI yet. ReplicaMD drives Claude Code, Codex, Gemini and others; it does not ship a model or resell tokens.
- You need managed team accounts, SSO or an audit trail today. It is a local tool, and that is a deliberate trade.
Works with
The CLI you already pay for.
ReplicaMD launches these in real terminals under your own logins. It does not proxy your prompts, resell tokens, or add a model of its own. Different members can run different runtimes in the same team.
Requirements
- macOS
- 13 Ventura or newer, Apple Silicon or Intel
- Windows
- 10 or 11, with Git for Windows (terminals run Git Bash)
- Linux
- A modern 64-bit distribution with glibc 2.31+
- Git
- Required - members work in real repositories and worktrees
- An AI CLI
- At least one: Claude Code, Codex, Gemini, OpenCode, Copilot, Cursor or Ollama
- Disk
- ~600 MB for the app; each agent member keeps its own checkout
Where your data lives
Four paths. That is the whole list.
No server receives your code, your prompts or your notes. Uninstalling means deleting a folder.
~/.replicamd/agents/<id>/One folder per AI member: its checkout, its memory files, its runtime config.~/.replicamd/plugins/<slug>/Installed plugins, as ordinary files you can read, edit or delete by hand.~/.replicamd/local.dbSQLite: your teams, members and tab layout. Nothing from your code.Your own foldersThe work itself. ReplicaMD reads and writes where you point it, and nowhere else.Free while it is being built in the open.
No trial, no seat count, no feature held back to sell later. If paid plans arrive they will be for hosted collaboration — the local workflow stays free, because charging for it would mean charging you for your own machine.
- Runs offline once your CLI is signed in
- Your repos stay where they are
- Plain Markdown memory