External Automation

External Automation

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 guide assumes AIWG is already installed and the agent-owned context regeneration procedure has connected the agent to this project.

AIWG does not currently ship a production resident daemon or scheduler command. The installed CLI has no the agent-owned daemon operation, the agent-owned schedule operation, or the agent-owned daemon operation entry point.

What is available

  • the agent-owned daemon-init operation scaffolds daemon configuration for development and future

compatibility. It does not start a process.

  • Provider-native scheduling tools may be used when they are present in the

active agent tool surface.

  • For Codex and other headless provider CLIs, an operator-owned system cron,

systemd timer, or CI workflow may launch a reviewed single-shot command.

  • the agent-owned job operation, the agent-owned job operation, and the agent-owned job operation

provide the reviewed external-job contract, starter scheduler configuration, and bounded single-shot execution. They do not create or manage a scheduler.

Ownership boundary

The external scheduler owns time, trigger retries, and host-level service lifecycle. The external-job runner owns its work-item claim, execution record, and idempotency checks. The provider owns model execution. AIWG must only claim contract validation, orchestration, and evidence handling when corresponding registered CLI commands exist.

For Gitea-backed Codex jobs, start with the versioned external-job contract and render a reviewed cron, systemd, or Gitea Actions example:

Use AIWG to complete this documented outcome: For Gitea-backed Codex jobs, start with the versioned external-job contract and render a reviewed cron, systemd, or Gitea Actions example
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Keep protected values out of arguments and repository files. See External-trigger jobs for the complete contract, approval, claim, idempotency, and evidence requirements. For other provider CLIs, create the scheduler configuration manually and review it as deployment code.

Check the current surface before following examples:

Use AIWG to complete this documented outcome: Check the current surface before following examples
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Historical daemon architecture remains under `tools/daemon/` and `agentic/code/addons/daemon/`; those sources are not evidence that the command is installed.