Docs

How ReplicaMD works, from first folder to finished work.

The whole operating model on one readable page. No architecture maze and no separate how-it-works page.

1. Open your real project

Choose a folder already on your machine. ReplicaMD does not upload or duplicate it into a cloud workspace.

2. Add the members you need

Pick Codex, Claude Code, Gemini, OpenCode, Copilot, Cursor, or a local Ollama model. Each member has an editable role and instructions.

3. Give the team one clear goal

Write the outcome you need. ReplicaMD keeps the work visible so you can inspect decisions instead of trusting a hidden chain.

4. Work safely in parallel

Members use separate Git worktrees. One experiment cannot silently overwrite another or damage your main checkout.

5. Review what changed

Terminals, Git state, notes, and files stay close together. You decide what becomes part of the project.

6. Return without rebuilding context

Close ReplicaMD when the day is done. Your local workspace and project memory are there when you come back.

Local first

What stays on your machine

Your repositories, notes, terminal sessions, and provider sign-ins remain under your control. ReplicaMD stores only the local workspace information needed to put your day back together.

A plugin is readable JavaScript, not a black box

This small example shows the shape of a command plugin. JavaScript details are highlighted so the important behavior is easy to scan.

export const plugin = {
  name: "focus-check",
  description: "Show the next useful action",
  async run({ project }) {
    const next = await project.findNextAction();
    return { message: next ?? "Choose one clear goal" };
  },
};

Understand the system. Then trust your own work.

See how it works Plugins