Operations
Day-two operation of the AGH daemon — process supervision, SQLite backup and inspection, troubleshooting, and production readiness.
- Audience
- Operators running durable agent work
- Focus
- Operations guidance shaped for scanability, day-two clarity, and operator context.
This section is for keeping AGH running. It covers daemon supervision, database state, the diagnostic flow when something misbehaves, and the production readiness checklist before AGH runs unattended in a real environment.
Use it after the happy path works. Getting started pages show how to launch the daemon; operations pages show how to prove it is healthy, where state lives, what to back up, and which checks matter before a long-running agent workflow depends on AGH. Most operators should read the daemon page once, then keep troubleshooting and production readiness nearby for incidents and release preparation.
The database page is intentionally separate from the daemon page because AGH has two persistence layers: the global catalog and per-session event stores. When a session looks wrong in the UI or CLI, check daemon health first, then inspect the relevant database path with the backup and recovery rules from this section.
In this section
Daemon
Daemon operations
Use this page when starting, stopping, restarting, or supervising AGH as a long-lived process.
Database
Database operations
Use this page when backing up SQLite, inspecting stored sessions, or retiring session directories.
Diagnose
Troubleshooting
Use this page when an operational command fails or the daemon misbehaves.
Checklist
Production checklist
Use this page before running AGH unattended in a real environment.