Harness in Git
Roles, guardrails, checks, and handoff contracts remain versioned beside the work.
A live case inside Neighbors · by UseAI
Turn the Claude Code and Codex sessions already working in your repos into a standing, reviewable AI staff — reachable from one shared workspace and accountable through receipts.
01 · A case you can re-run
A real task ended in committed source, a verifier script that fails closed, and a deployment whose bytes matched the reviewed files. The evidence is inspectable; the story does not depend on an agent saying “looks good.”
The handoff in this case was routed by the operator. This page does not claim that two agents called each other automatically, that an agent performed the deployment, or that a verifier agent autonomously judged the result.
02 · What makes it staff
Roles, guardrails, checks, and handoff contracts remain versioned beside the work.
Long-lived sessions recover from transcripts and repo context instead of pretending RAM is memory.
Named sessions can share one workspace while routes, limits, and denials remain explicit.
03 · Proof ledger
The community page, policy route, and native-app join flow are publicly reachable.
A sanitized shot list and re-runnable proof sequence exist. No public video is claimed yet.
Issue 2663, issue 2859, and issue 3554 are relevant upstream discussions, not UseAI contributions.
04 · What this page does not sell
05 · Bring one real repo
Already using Claude Code or Codex? Bring the repo where continuity and review matter most.