CLI reference

Boots the dashboard and opens the sign-in gate, then serves http://localhost:4000. This is the command the desktop app runs for you; type it when you want the server in a terminal you control.

repoops run

Writes a .claude/brain/ into a repo that has none. The scaffolder reads the same canonical tab registry the dashboard renders from, so a fresh brain matches what the dashboard expects. Hand the generated brain-bootstrap-prompt.md to your coding agent to fill the stubs with real content.

repoops init [dir]

Registers a repo with the dashboard so its brain, docs, and telemetry appear alongside everything else you track.

repoops add [path]

Stops tracking a repo. It leaves the repo and its brain on disk; only the dashboard's registration goes away.

repoops remove <id|path>

Checks a repo's brain and its wiring into the dashboard, and names what is missing. Run it when a tab is empty and you cannot tell whether the fault is the repo or the server.

repoops doctor [dir]

Binds this install to a team using a one-time code from /team/connect. Until you run it, the install is a solo one and nothing leaves the machine.

repoops connect <code>

Answers who wrote a line, where the answer includes the agent. Given a file it reports the session and prompt behind each line; given a commit it reports the agent and human split.

repoops blame <file>

Runs the accountability metrics against this repo and prints the real numbers, not a sample. It reads local evidence only, so the figures are yours and nothing is uploaded. The published figures on /accountability-benchmark come from this command run against RepoOps itself.

repoops bench

Reads a Git AI refs/notes/ai note and maps it into a RepoOps proposal, so attribution captured by another tool lands in the same ledger. Only the git-ai source is wired.

repoops import git-ai --dry-run

Agent memory is an input to every run, which makes it worth poisoning. Sign records the state you sanctioned; verify checks the current .claude/ brain and CLAUDE.md against those signatures and flags what changed without your say-so.

repoops memory verify

repoops memory sign

The same signed-state check, applied to what your skills and subagents are allowed to do. Sign records each capability manifest; verify reports drift from it.

repoops skills verify

repoops skills sign

Snapshot and restore the working tree without a commit and without moving HEAD. Use it before letting an agent make a large change, so undoing it costs one command rather than a rebase.

repoops checkpoint <cmd>

Inventories the long-lived secrets a non-human identity on this machine can read, and reports which are over-exposed for what the agent actually does. Discovery only: it reads, it does not rotate.

repoops nhi

A loopback-only credential broker, so the agent holds a short-lived task-scoped token instead of your raw key. Opt in and it mints on demand; leave it off and nothing listens.

repoops broker

One day-one score out of 100 from local discovery plus the advisory detectors, with the top five fixes named. The starting point when you want to know where a repo stands before picking a specific scan.

repoops readiness

Scores this repo's resistance to prompt injection by running a probe corpus against your agent configuration, and treats the score as an eval bar: it exits non-zero when the repo does not clear it, so CI can hold the line.

repoops injection-eval

Shows or edits the pinned domains and IPs a repo's sandbox may reach. An agent that cannot resolve an unexpected host cannot quietly exfiltrate to one.

repoops egress-policy

Reads the MCP servers you have configured and reports definition drift, the tool-poisoning case where a server's tool description changes under you after you approved it.

repoops mcp-scan

Pins the MCP servers you approve and lists what mcp-scan has flagged against those pins.

repoops mcp-allow

Attacks your own MCP setup with a library of tool-poisoning attacks and reports which ones land. Where mcp-scan watches for drift, this one goes looking.

repoops redteam-mcp

Checks an AI-authorship attestation offline: no server, no network, no account. A tampered or unknown record fails honestly, and the verdict is the same one the dashboard page gives. --key is the install's public verification material, never a private signing key.

repoops verify <record>

Grades a third-party emitter's attestation against the v0.2 conformance suite, check by check (graded band, honest-null cost, digest, signature). --key is optional; without it the signature check is skipped rather than faked.

repoops conform <record>

Reports the Wave B public-claims preconditions and which of them this install currently meets.

repoops go-live

The capture pass on a bound install: read new session evidence, buffer it, push it. Run it once, or run it as a daemon that repeats on an interval. With --otlp-receive the daemon also hosts a loopback OTLP/HTTP receiver, so OTLP-emitting tools can push into a bare Sensor with no other agent installed.

repoops sensor --once

repoops sensor --watch

repoops sensor --watch --otlp-receive

An optional in-path tee for capture. The Sensor is the supported default and this is an unsupported beta; reach for it only when a passive pass genuinely cannot see what you need.

repoops tap --help

Mints the enrollment secret a headless install passes to `sensor --enroll`, so a fleet machine can bind with no browser. Owner or admin only.

repoops enroll-secret mint

Scaffolds one of the named forward-deployed engagement deliverables. The mcp kind takes --connector, --auth, and --no-eval; the others take the name alone.

repoops fde new <kind> <name>