Skip to content
Agent Hub

State And Audit

Agent Hub uses persistent state so a restart does not erase the workflow.

Registry

Section titled “Registry”

The registry stores sessions, queues, active work items, pending messages, review records, deploy runs, reconciliation runs, and project metadata. Registry writes use a revision guard so one Hub process cannot silently overwrite newer state from another process.

Event Journal

Section titled “Event Journal”

Structured worker events are appended to a journal. A rebuildable projection summarizes the current state for status and health checks.

Audit Command

Section titled “Audit Command”

Use:

Terminal window
hub audit [session|project|run-id] --json

Audit answers questions like:

  • What instruction is active?
  • What is queued?
  • Was the latest delivery acknowledged?
  • Which pending messages are open?
  • Which work item superseded another?
  • Which review, deploy, or reconciliation run is active?
  • What event evidence exists?

Health Command

Section titled “Health Command”

Use:

Terminal window
hub health [session|project|run-id] --json

Health reports readiness and exact fix steps for:

  • missing binaries
  • event-store issues
  • dead watcher
  • Remote Control problems
  • protocol disagreements
  • pending reviews
  • safe repair opportunities
  • active run blockers
Audit explains history. Health explains what to fix next.