Skip to content

Operations

Day-two operation of the CompozyOS daemon — process supervision, SQLite backup and inspection, troubleshooting, and production readiness.

For people running agent work8 pages in this section

This section is for keeping CompozyOS running. It covers daemon supervision, database state, the diagnostic flow when something misbehaves, and the production readiness checklist before CompozyOS 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 run depends on CompozyOS. 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 CompozyOS 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.

Remote access has its own section: the Gateway pages cover reaching the daemon from other devices, receiving webhooks from the internet, and the security model behind both.

In this section

On this page