Verify, repair, backfill, and back up Pi/Claude/Codex session capture across active machines. Use when checking whether agent activity is captured, reviewing capture outbox backlogs, backing transcripts up to NAS, or scheduling capture verification.
69
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Use this skill when Joel asks whether agent activity is being captured, indexed, or backed up across machines.
Transcript/raw activity sources:
~/.pi/agent/sessions, ~/.pi/agent/run-history.jsonl, ~/.pi/notes-bridge/events.jsonl~/.claude/projects~/.codex/sessions, ~/.codex/archived_sessions, ~/.codex/session_index.jsonl~/.joelclaw/runs-dev~/.joelclaw/outbox is the legacy outbox, not complete capture coverage.NAS audit mirror:
/Volumes/services/joelclaw/sessions/<machine>/<source-key>/.../Volumes/services/joelclaw/sessions/receipts/*.jsonThe separate additive raw archive has full and priority server receipts plus local steward receipts. For its root and receipt paths, see the private operator map. Do not confuse this archive with the cross-machine audit mirror. An hourly priority job, com.joelclaw.raw-transcript-backup, is being added; verify its deployment and fresh receipts before treating it as active.
Capture routing:
http://127.0.0.1:3111/api/runs; health: http://127.0.0.1:3111/api/runs/health.Panda is retired, not a live capture host, Central, or relay. Remove it from routine host lists. Capture authentication uses Flagg's persistent local ~/.joelclaw/capture-auth.db; Typesense machines_dev is only its enrollment/migration mirror.
From ~/Code/joelhooks/joelclaw-runtime, this Flagg-only metadata audit writes a receipt but does not sync, repair environment files, or replay payloads:
bun scripts/agent-session-audit-backup.ts \
--hosts flagg \
--central-url http://127.0.0.1:3111 \
--backup-root /Volumes/services/joelclaw/sessions \
--sync=falseFor satellites, select active hosts and an approved Central URL reachable from each selected host. Do not rely on the script's historical host or endpoint defaults.
Audit script behavior:
JOELCLAW_CENTRAL_URL in .zshrc, .zprofile, and ~/.config/system-bus.env--repair-env (repairEnv in the scheduled event), --sync=true, and outbox replay are mutations requiring a repair request. Authorization for verification alone does not authorize them. For metadata-only verification, use --sync=false and omit repair and replay flags. Raw transcript content still requires the session evidence receipt.
The audit script rejects its old --replay-outbox, --replay-limit, and --replay-max-bytes flags. Use scripts/replay-capture-outbox.ts for separately requested, bounded replay. Review its catalog, checkpoint, and per-batch receipts against stored hashes and index coverage. Preserve queued payloads. Check worker/Inngest health before replay; do not unleash a large backlog.
Host worker function:
system/agent-session.capture-backup.verifysystem/agent-session.capture-backup.requestedTZ=America/Los_Angeles 15 5 * * *Manual trigger for a requested Flagg backup:
joelclaw send system/agent-session.capture-backup.requested -d '{
"hosts": "flagg",
"centralUrl": "http://127.0.0.1:3111",
"repairEnv": false
}'The scheduled worker syncs backups even with repairEnv:false; this is not metadata-only verification. It defaults repairEnv to true when omitted. Review cron repair ownership and explicit hosts/routing before relying on it. Replay is separate work, not part of this event.
centralHealthOk=true./Volumes/services/joelclaw/sessions/receipts. Raw archive coverage needs its separate full/priority and local steward receipts; see the private operator map.runs-dev, and outbox metadata. An unreachable host or failed source sync remains unverified.~/.joelclaw/auth.json; the script reads them locally on each host.aa0116c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.