Install

Install the binary, connect your harness, and check the connection.

One binary, ledger and library serve every harness; an adapter only forwards what its harness exposes. omp is the reference. What each harness can and cannot do: harness capabilities.

Install

omp

You need omp 18.12 and a Rust toolchain, in a checkout of this repo.

1. Build and link:

   scripts/install.sh

   It builds the binary, links the extension into omp, and writes the shim ~/.local/bin/rematch.

2. Check:

   rematch doctor --text

   The last line reads ready: true. Anything else is listed as a problem: line saying what to run.

What install.sh does

• cargo build --release (--locked when Cargo.lock exists).
• Links extension/agents → ~/.rematch/agents (for subagent entries).
• omp plugin link extension --scope user.
• Writes ~/.local/bin/rematch, which runs target/release/rematch of the checkout.
• Runs rematch doctor and prints the optional model roles.

Windows

Turn on Developer Mode (Settings → System → For developers): every library view is a symlink, and Windows lets a normal user create one only there. rematch doctor reports it as a problem: otherwise. Then run, in PowerShell:

powershell -ExecutionPolicy Bypass -File scripts\install.ps1

It does what install.sh does; the shim is ~\.local\bin\rematch.exe, a symlink to target\release\rematch.exe, and that directory is added to your user PATH. scripts\uninstall.ps1 undoes it.

Claude Code

You need Claude Code 2.1.285 or later and the rematch binary: cargo build --release in this repo, rematch on PATH, or REMATCH_BIN set.

1. Load the plugin in every session:

   ln -s /path/to/rematch/adapters/claude-code ~/.claude/skills/rematch

   Or for one session only:

   claude --plugin-dir /path/to/rematch/adapters/claude-code

2. Check the load:

   claude --plugin-dir /path/to/rematch/adapters/claude-code plugin details rematch

   Expect 8 hooks; under Skills, the eight commands plus every linked skill; under Agents, the rematch subagents.

Use one of the two routes above

A marketplace install copies the plugin and drops its skills/ link. ~/.claude/plugins/ is Claude Code’s marketplace cache.

Reflection makes its model calls through omp (OMP_BIN, else omp on PATH). Without omp, sessions are still traced, flagged and loaded; run rematch reflect --pending where omp is installed.

If large sessions end unflagged, raise the 1.5 s SessionEnd budget:

CLAUDE_CODE_SESSIONEND_HOOKS_TIMEOUT_MS=5000 claude

Pi

Use Pi 1.4.x (@earendil-works/pi-coding-agent) and Node 22.19 or newer. Keep this checkout available: the adapter imports Rematch’s shared helpers from it.

1. Build Rematch and put its binary on your shell’s path:

   cargo build --release
   export PATH="$PWD/target/release:$PATH"

2. Install the local Pi package:

   pi install "$PWD/adapters/pi"

   For one session instead:

   pi -e "$PWD/adapters/pi"

3. Start Pi and check:

   /rematch status

Pi discovers ~/.rematch/skills through its native resource-discovery hook. Tracing and approved runtime hooks run in Pi; background reflection still needs omp with configured model access.

Which Pi?

This adapter targets the maintained @earendil-works/pi-coding-agent package. The older @mariozechner/pi-coding-agent package is not the tested target.

Remove the package with pi remove /path/to/rematch/adapters/pi. See the adapter notes for session resume behavior and limits.

OpenCode

Use OpenCode 1.19.4 and a local Rematch checkout. OpenCode 2 is not a tested target.

1. Build the Rematch binary:

   cargo build --release
   export PATH="$PWD/target/release:$PATH"

2. Add this entry to the existing plugin array in your global ~/.config/opencode/opencode.json, or a project’s opencode.json:

   {
     "plugin": ["/path/to/rematch/adapters/opencode"]
   }

   Merge it with your existing configuration; do not replace other plugins.

3. Start OpenCode and check:

   /rematch-status

The plugin adds Rematch’s shared directory to OpenCode’s in-memory skill paths. It traces main sessions, runs approved hooks, and provides user commands for approvals. Reflection still needs omp with configured model access.

Finishing a session

OpenCode’s idle event ends a turn, not the session. Rematch waits for process disposal, crash recovery or its documented quiet-session cutoff before finalizing evidence. A later continuation gets a new trace segment rather than rewriting counted history.

See the OpenCode adapter for supported hooks, session boundaries and history import.

Codex

You need rematch on PATH (scripts/install.sh, or cargo build --release). The omp plugin is not required. Nothing runs inside a Codex session; rematch reads its sessions afterwards.

1. Let Codex see rematch’s skills (once):

   mkdir -p ~/.agents/skills
   ln -s ~/.rematch/skills ~/.agents/skills/rematch

2. Before starting Codex in a repo, add the skills that match it:

   rematch skills sync --harness codex --cwd "$PWD"

   To do it on every launch, add this to your shell rc:

   codex() { rematch skills sync --harness codex --cwd "$PWD" >/dev/null; command codex "$@"; }

3. After you worked, import and reflect:

   rematch import --history --harness codex
   rematch reflect --history

   A session that was never imported never counts.

4. Optional: digest, sync and approvals from inside Codex, each command after your approval:

   ln -s "$PWD/adapters/codex/skills/rematch-status" ~/.agents/skills/rematch-status

Choose the models (optional)

The editor should be the strongest model you have, the classifier a fast one. Set them in ~/.omp/agent/config.yml:

modelRoles:
  rematch-editor: <provider>/<strongest model>      # falls back to slow → default
  rematch-classifier: <provider>/<fast model>       # falls back to smol → tiny → default

rematch doctor --text shows which models it resolved. Per-machine roles: model roles.

Seed from your history (optional)

Import the sessions you already have, then reflect on the ones that carried a correction. Import is read-only and makes no model call.

rematch import --history
rematch reflect --history

• import --history reads available omp, Claude Code, Codex, Pi and OpenCode history. Use --harness omp|claude-code|codex|pi|opencode to select one, or --skip-profile <name> to exclude an omp profile. Each adapter documents its history location and environment overrides.
• reflect --history handles the newest 10 flagged sessions per run (--limit, --since 2026-10-01). Run it again for the next batch; a session is reflected once.
• Each reflection follows the same rules as a live one: same rate limits, at most 3 model calls.

Next: your first correction