AGENTS

An agent that works like a careful colleague

Delegate an item and the agent's session wakes by itself. It gets one context pack with every wiki fact marked by who last checked it, an obligation when its code touches a documented block, and a gate that will not let it stop until the doc follows the code. Everything it did is one list you can revert.

1:35 · ONE ITEM, ONE AGENT, END TO ENDDELEGATE → WAKE → PACK → WORK → EVIDENCE → GATE → REVIEWREAL COMPONENTS, THE PLUGIN'S OWN TEXT
0:00.00
1:35.00
WHAT HAPPENED

Nine steps, and who did each one.

  1. 01Hand overAyşe delegates FER-151 to Claude. The assignee stays hers; the agent sits beside it as the delegate, and its inbox counts one.
  2. 02WakeThe Claude Code session wakes on its own, begins a session, takes the notification from its inbox and claims the item. The lease is its hand on the item, and it runs out if the agent goes quiet.
  3. 03Context packThe context pack arrives in six layers: the item, its comments, its relations, the linked pages, the project and the workspace. Every wiki block carries who last verified it and when, so a stale fact looks stale.
  4. 04WorkThe agent edits a file that ferrow.toml maps to a block of the Billing page. Ferrow opens an obligation on the spot, and the commit carries the item's key as a trailer.
  5. 05EvidenceWhat the agent relied on, it confirms; what the code now contradicts, it flags, with the line that proves it. The page shows both marks in place.
  6. 06Read setAyşe changes a price on the page while the agent works. The agent read that block, so the band tells it before it stops; it re-reads and confirms the change does not touch its work.
  7. 07GateThe agent tries to stop. The Stop hook holds the session until the block is rewritten and the obligation satisfied, then the summary comment goes on the item and the lease is released.
  8. 08Back in FerrowBack in Ferrow: the session drawer lists every change with a Revert session button, the agents row shows its usage, the decision it proposed waits for acceptance, and a person, not the agent, is asked whether an old fact still holds.
  9. 09CloseThe same protocol runs in Claude Code, Codex, Hermes and an unattended daemon.
IT RUNS WHERE YOUR AGENT RUNS

One protocol, five ways in.

Claude CodeA plugin: the MCP server, the skill, the hooks and the band above the prompt.
CodexThe same MCP server and a hook shim, trusted once with /hooks.
HermesMCP for the tools and a signed webhook that wakes it when its inbox fills.
The daemonNobody at the keyboard: it takes the inbox, opens a worktree per item and runs Claude or Codex in it.
Claude RoutinesNo machine of your own: the repository carries the config and Ferrow fires the routine.
Bring one project over this afternoon.Import brings your items and comments, and old keys stay searchable. If it doesn't fit, export and leave; it's your data.
Start freeRead the import guide