Daemon Addon Status

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

First time using AIWG? Begin with Install, Connect, and Verify. This status page assumes AIWG is already installed and the agent-owned context regeneration procedure has connected the agent to this project.

The daemon addon contains design artifacts and configuration scaffolding, but the production AIWG CLI does not currently register a resident `daemon` command. Consequently there is no supported start, status, stop, PTY, or scheduler quickstart in this release.

the agent-owned daemon-init operation may be used to inspect or scaffold configuration for development work:

Use AIWG to complete this documented outcome: the agent-owned daemon-init operation may be used to inspect or scaffold configuration for development work
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

That command does not start a daemon. Verify the installed top-level surface with:

Use AIWG to complete this documented outcome: That command does not start a daemon. Verify the installed top-level surface with
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

For recurring work, use a provider-native scheduler when available or an operator-owned external scheduler such as system cron, a systemd timer, or CI. Do not use the agent-owned schedule operation, the agent-owned daemon operation, or the agent-owned daemon operation; those commands are not registered.

For approval-gated Gitea work executed by Codex, use the separate single-shot the agent-owned job operation, the agent-owned job operation, and the agent-owned job operation surface. Those commands validate and execute a reviewed job while the external service continues to own the schedule. See the public External-trigger jobs guide.

A future daemon release must land command registration, lifecycle handlers, help text, tests, and documentation together before this guide can advertise runtime operations.