GET STARTED

A first review,
without the guesswork.

Install only what you need. Keep the project you want reviewed as the working directory. Let your agent close the review loop.

Recommended: let your agent verify the release first

Install or upgrade in one line →

A clone starts on the default branch, which can contain unreleased work. Before executing the manual installer below, select the published signed release, verify its expected signing identity and package hash, and read its installer help. The copyable prompt covers those steps and asks before installing missing prerequisites.

01 Verify, then install only MOMM

Use the new-install and legacy bootstrap guide to prepare an exact signed release in a permanent directory before executing its code. The separately trusted bootstrap helper checks tools first and never installs or replaces an existing link. Keep the verified clone: your harness will link to it.

Which harness should discover the skill?

1. Preview only

node momm/scripts/install.mjs --target codex --dry-run

Read the preview before choosing to run the separate installation command:

2. Install only after approving the preview

node momm/scripts/install.mjs --target codex

Restart or refresh your agent’s skill discovery if needed. --target all is an explicit multi-harness choice; root install.mjs installs the whole collection.

The installer records the successful harnesses and their exact skill scopes in momm.lock under Git’s local MOMM state directory. It never overwrites existing discovery paths.

02 Connect a reviewer

From the skills clone, open the local Setup Center:

Open Setup Center

node momm/scripts/setup-ui.mjs

Choose your current agent as governor. Use the provider’s login action and complete the browser login yourself. Quick Setup can test detected sessions with a disclosed synthetic sentence—not your project source.

The page opens on a local, automatically chosen port. In a headless session, use node momm/scripts/onboard.mjs --governor codex. Installed credentials are evidence, not a promise that the next dispatch will succeed.

03 Review the right project

Open the project you want reviewed in your agent. Paste this:

Paste into your agent

Use $momm to review my current changes. Keep this project as the working directory. Use at least one ready external reviewer, reproduce material findings before authoring fixes, record every suggestion’s disposition, and show me the private ledger link.

Prefer the terminal? Codex on macOS / Linux

Run from your project

node "$HOME/.agents/skills/momm/scripts/multi-review.mjs" --preflight --governor codex --pretty
node "$HOME/.agents/skills/momm/scripts/multi-review.mjs" --governor codex --min-success 1 --pretty

Codex on Windows / PowerShell

Run from your project

node "$env:USERPROFILE/.agents/skills/momm/scripts/multi-review.mjs" --preflight --governor codex --pretty
node "$env:USERPROFILE/.agents/skills/momm/scripts/multi-review.mjs" --governor codex --min-success 1 --pretty

04 Close the loop

Reviewer replies are only the first half. The governor investigates material findings, authors any supported fixes, tests them, and records every suggestion as applied, rejected or deferred with a reason.

Applied decisions need checkable evidence: a regression test, a commit or a concrete probe. A deferred item is still open work. Run node <installed-momm>/scripts/governor.mjs --run <run_id> from the project. It matches stable item IDs to decisions and verifies original report/input binding and recorded source, test and output hashes. Missing, duplicate, deferred or stale evidence stays incomplete. Add --record only after checks pass; this saves a separate receipt and rebuilds the private ledger. The validator never executes reviewer snippets and cannot independently prove an observation was honestly recorded or a test adequate.

Your agent appends decisions to your project’s .ensemble_reviews/dispositions.jsonl, joined to the report’s run_id. Zero dispositions can mean no suggestions existed—or an unfinished review. Check the actual report.

05 Open your private dashboard

The agent should relay the ledger link after every completed run. To rebuild it yourself after adding decisions, run this from the same project:

macOS / Linux · Codex

node "$HOME/.agents/skills/momm/scripts/ledger.mjs" --open

PowerShell · Codex

node "$env:USERPROFILE/.agents/skills/momm/scripts/ledger.mjs" --open

This opens the local .ensemble_reviews/ledger.html. It is not the public evidence website. Keep the evidence directory private and out of temporary folders.

Something did not work? Start with the actual status →