Agents

Fabric is agent-native: a coding agent drives the exact same loop a person does, through the same reviewed path into trunk. There is no special agent mode to learn, just the CLI.

Why it fits agents

Non-interactive. Every command takes args and flags directly and never prompts. Pass --json and you get machine-readable output for every command.
Idempotent push. fabric push is safe to re-run: it appends only what’s new, so an agent can retry without making a mess.
Local, network-free inspection. fabric status and fabric diff need no round-trip, so an agent can check its own work cheaply.
Review is policy-driven. An agent goes through propose → approve → accept like everyone else. Whether a change needs approval before it lands, and from whom, is set in the repo’s fabric.yaml (see Configuration). An agent cannot bypass the policy the repo configured.

The loop, for an agent

fabric change create "implement feature X" --json
fabric clone --json
cd implement-feature-x
#   …agent edits files…
fabric push --json
fabric propose --json
fabric approve --json     # if the repo's policy lets the change be approved this way
fabric accept --json      # blocked until fabric.yaml's approval policy is met

The zero-context primer

Point an agent at Fabric’s primer for a self-contained, copy-pasteable mental model and command set:

curl https://app.fabricemr.com/agents.md

It’s the 5-minute version of these docs, written for an agent that already knows Git. Fabric also serves its own installer (curl -fsSL https://app.fabricemr.com/install.sh | sh), so a fresh agent box needs no checkout.

Rules of thumb

One change = one reviewable unit of work. Open another change for unrelated edits rather than piling everything onto one.
Trust fabric <cmd> --help over guessing: it’s always current.
Op refs are actor:seq, not content hashes.