queue
ak content queue
Inspect, remove, or attempt entries in the persistent scheduled-post queue.
Use ak content queue as the namespace for the persistent delivery queue.
Calling it without a subcommand prints help and does not read or write the
queue.
Usage
ak content queueThe command accepts no documented positional arguments and has no aliases.
Commands
| Command | Effect |
|---|---|
ak content queue list | Read all pending, published, and failed entries. |
ak content queue cancel <id> | Remove one entry and atomically replace the queue file. |
ak content queue run-pending | Attempt due pending entries and update their state. |
Entries are created by ak content publish --at in
~/.agentkit/content/queue.json; AGENTKIT_HOME changes the base. The parent
command does not create that file. Queue entries retain rendered bodies,
timestamps, attempt state, errors, and adapter metadata. With Discord,
metadata can include the webhook URL in plaintext.
The queue directory is created with mode 0700, and atomic saves use a 0600
temporary file. There is no backup, restore, prune, or replay command. Published
and failed rows remain until explicitly removed.
Output and exit status
The bare namespace writes help to stdout and exits 0. Flag-parse failures are
plain text and exit 2. Each leaf command owns its own JSON and mutation
contract.