Validate agent capture before you roll out Relay org-wide

Platform teams should prove capture end-to-end on one machine before asking every developer to install Relay. This checklist takes about thirty minutes.

Step 1 — Local hook verification

After install, run:

relay run --local -- echo "offline capture check"

--local writes a local capture without calling the API. Confirm the command exits zero and prints a capture summary.

Step 2 — Live API smoke test

Authenticate if needed:

relay auth

Run a wrapped command against the dev API:

relay run -- echo "live capture check"

Check relay status for the registered environment ID.

Step 3 — Cursor task on a real repo

Pick an internal repository (not production secrets). In Cursor:

Start an agent task that reads at least one file and runs one tool.
Finish the task completely.

Verify nested auto-collect files grew:

find ~/.relay/captures -name '*.json' -not -name 'watch-*.json'

Step 4 — Upload and confirm in Architect

relay sync

Open Architect → Sessions. The new session should show:

Environment name matching relay status
Tool-call timeline entries
Timestamps aligned with your Cursor task

Step 5 — Rollout gate

Check	Pass criteria
Hooks	New `~/.relay/captures/<agentId>/<sessionId>.json` files after each agent task
Sync	`relay sync` returns success without auth errors
Architect	Session appears within one minute of sync
Secrets	No adapter tokens in capture JSON (use org vault)

If any row fails, fix on the pilot machine before broadcasting install instructions org-wide.