3.0.0-beta.15). Features may change before the next stable release.Switch to stable →schedule
ak content schedule
Start and supervise the foreground scheduler that delivers due persistent queue entries.
Use ak content schedule as the namespace for continuous scheduled delivery.
Calling it without a subcommand prints help and starts no process.
Usage
ak content scheduleThe command accepts no documented positional arguments and has no aliases.
Command
ak content schedule daemon runs one queue pass immediately, then polls again
at the configured interval until SIGINT or SIGTERM. Despite its name, it
does not detach, install a service, write a PID file, or restart itself. Run it
under your own service manager when persistence across sessions is required.
The scheduler uses the webhook credential stored with each queue entry. It does
not use AgentKit authentication or entitlements. Each pass can write both the
external channel and ~/.agentkit/content/queue.json.
Output and exit status
The bare namespace writes help to stdout and exits 0. With --json enabled,
unknown or invalid flags use the shared JSON stderr error envelope
(error_code: validation_failed, exit 2). Human mode, including --json=false,
prints Usage. The daemon has a streaming stderr contract rather than a normal
JSON result.