An OMP plugin for models that talk through a task, agree on a split, and work together.

Choose two models and give them a goal. Duo connects them through OMP's Agent Hub messages, with a shared workspace, working notes, and a live board showing who is doing what. Each model runs its own conversation; Duo does not share KV caches or model weights.

Get started

With OMP installed and your models authenticated, install Duo in your terminal:

omp plugin install github:ashhart/Duo

From a terminal in your project, launch OMP straight into Duo:

omp "/duo"

Duo shows two pickers: choose your first model, then choose its partner. Press Enter to confirm each choice, or Escape to cancel without changing your model.

Already inside OMP? Type the slash command there:

/duo

Both routes open the same two pickers. Once the room opens, type a task normally:

Add search to this app, agree on who owns the implementation and tests, and check each other's work.

You can also supply both model IDs from the terminal:

omp "/duo provider/model-a provider/model-b"

Or, when already inside OMP:

/duo provider/model-a provider/model-b

These are placeholders: use /duo models inside OMP to see your configured IDs. The first model becomes your visible session; the second joins as its partner. You can select the same model twice to open two sessions. If you have already chosen your first model in OMP, add only its partner:

/duo provider/model-b

Duo uses your existing OMP providers, so it needs no separate API keys or config file. If OMP is already running when you install or update Duo, restart it first. For a fresh OMP installation, follow OMP's setup instructions and configure at least one working model before starting Duo. Provider setup and any model downloads take additional time.

A conversation you can follow

An illustrative exchange:

Model A  PROPOSE I'll handle search; can you own the tests?
Model B  ASK q1 Should search include archived items?
Model A  ANSWER q1 No, only active items.
Model B  AGREE I'll own the tests, including archived-item exclusion.

Messages appear in the main chat and update a board above the editor:

duo room · Model A + Model B
you   ▸ implementing search
peer  ▸ testing search and archived-item exclusion

Both models can inspect and edit your project. They are prompted to negotiate ownership before editing, challenge each other's assumptions, and verify the result together. The visible session records their agreement in OMP's todo list; the peer runs in a background task and communicates through Agent Hub.

Commands

Run these slash commands inside OMP; from your terminal, use omp "/duo".

Shared working notes live in .omp/duo/notes.md in your project. To change partners, run /duo stop, wait for closure, then start another room. Selecting two models changes your visible OMP model; it stays selected after the room closes. Room configuration is saved with the OMP session and restored when you resume it. Open questions appear on the board while the room is running.

Requirements and troubleshooting

Duo is tested on OMP 18.2.6 and uses its model catalog, task agents, and Agent Hub. Both sessions use your existing providers and consume their usual tokens and compute; choosing the same model twice still opens two sessions.

The package keeps the name omp-local-duo so existing installations continue to work. To update, rerun the install command and restart OMP. To remove it, run omp plugin uninstall omp-local-duo.

Development

git clone https://github.com/ashhart/Duo.git
cd Duo
bun install --frozen-lockfile
bun run check

The regression suite covers room lifecycle, peer admission, cancellation, ASK/ANSWER tracking, message delivery, and session restoration. bun run typecheck checks the plugin's TypeScript against its host interface shim. For a full integration check against installed OMP, run bun run check:host. It installs the packed plugin into a temporary OMP configuration and verifies peer admission, native Hub ASK/ANSWER delivery, and question resolution using deterministic model fixtures, with no paid inference. For a smaller loading check without an inference request:

omp --no-session --no-title --no-extensions -e ./scripts/host-smoke.ts -p /duo-smoke

See room behavior for protocol and lifecycle details.