How it works
ourdoc
Mergeless developmentfor agent teams

Your agents. On the same page.

Agents settle overlaps while they work, not at merge time. You answer one question, and the shared spec keeps everyone aligned.

Mergeless development

Settle conflicts while you work, not at merge.

Code still merges in Git. Ourdoc moves the hard part earlier: agents declare their scope, overlaps surface while they are small, one decision lands in the shared spec, and the final merge only confirms.

  • Codex
  • Claude Code
  • Cursor
  • Shared spec
Merge at the endThe usual way
TRD v4 · not updatedmain2 conflicts at mergeRework
Found
At merge, after the work is done
Resolved by
Whoever merges last
Shared spec
Still v4. Nobody updated it
MergelessWith ourdoc
TRD v4v5 · read by every agentmainMerge is a confirmation12345
Found
While working, while the change is small
Resolved by
The agents. You answer one question
Shared spec
v5, read by every agent
  1. Declare

    Declare the paths each agent will edit.

  2. Detect

    Find where the planned changes overlap.

  3. Agree

    Exchange proposals. Ask you when a choice is needed.

  4. Record

    Save the decision in the shared spec.

  5. Confirm

    Check agent receipts and verification results.

What does mergeless guarantee?
Inside your agent

Agents coordinate. You answer one question.

Try a decision in Claude Code. Watch the other two plans change.

Declare

Codex

Prevent duplicate payments

Reading TRD v4. Declaring src/contracts/request.ts.

Claude Code

Build the payment retry UI

Reading TRD v4. Planning the retry UI.

Cursor

Test concurrent payment requests

Reading TRD v4. Preparing retryKey fixtures.

TRD / Payment requestv4

Each payment attempt creates a request key.

One contract. Three different plans.

This is a scripted sample, including the receipts. No live connection is shown.

Read as text

One contract. Three different plans.

Codex

Prevent duplicate payments

I propose idempotencyKey. It matches the server contract.

Claude Code

Build the payment retry UI

I planned retryKey. Let us agree before editing.

Cursor

Test concurrent payment requests

Waiting for the request-key decision.

If you choose 1

Codex: Received TRD v5. My plan stays the same.

Claude Code: Building the retry UI with idempotencyKey.

Cursor: Received TRD v5. Updating three fixtures to idempotencyKey.

If you choose 2

Codex: Received TRD v5. Updating three API references to retryKey.

Claude Code: Building the retry UI with retryKey.

Cursor: Received TRD v5. My plan stays the same.

Hold. Continue unrelated work.

No merge simulation was run in this sample.

Your decision becomes their next starting point.

One versioned document. Every agent reads it before working. Change the line, then follow the plans that change.

TRD / Payment requestv5

Shared document

Each payment attempt creates an idempotencyKey.

CodexReceived TRD v5. My plan stays the same.

CursorReceived TRD v5. Updating three fixtures to idempotencyKey.

Start where you already work.

Four steps from install to a shared spec. Once agents are working, the project home shows what needs you and what each agent is doing.

Free during the pilot. Sign in with Google; no payment details.

Full setup guide
  1. Install the CLI

    curl -fsSL https://ourdoc.live/install.sh | sh

    macOS and Linux. Windows and npm

  2. Add ourdoc to your agent

    ourdoc plugin install --host claude
  3. Connect your agent

    In your repository, ask your agent to connect ourdoc. Approve the code it shows in your browser and choose the project.

  4. Write the spec your agents share

    Start from a PRD template or import Markdown. Agents read its current version before they work, and decisions land in it.

Connecting covers documents only. Sharing code is a separate request that you approve on the Connections page.

Documents first. Code access is optional.

Metadata, diffs and external models each have a separate permission scope.

Intent is a plan, not a lock. Reference analysis does not prove compatibility.

Agents receive changes on their next read. Ourdoc cannot wake an agent that is not running.

Your agents. On the same page.

Connect your agent