ak watch
ak watch status
Read persisted watcher, post-count, rate-limit, PID-metadata, and log-path state without a network request.
Use ak watch status to inspect local watch records. It reports persisted state,
not independently verified process liveness.
Usage
ak watch status [owner/repo]The command has no command-specific flags and never prompts.
Scope and behavior
ak watch status
ak watch status owner/repo
ak watch status --jsonWithout an argument, the command enumerates
~/.agentkit/watch/*/state.json. Missing watch state is a successful empty
result. Corrupt or unreadable individual state files are silently skipped in
this all-repositories view. With owner/repo, missing, corrupt, or unsupported
state is an error instead.
The read also loads optional cli-meta.json fields such as PID, filters, agent,
and log path. It performs no GitHub request, process signal, state write, cache
write, or provider call.
An active: true row does not prove its PID exists or that a watcher is alive;
the command does no liveness check. Conversely, clearing state with
ak watch stop does not stop an already running loop. Verify the PID with your
operating-system process tools when controlling external mutations matters.
Output and exit status
Human stdout shows running state, repository, label, agent, sent count, configured
hourly ceiling, last poll, optional PID, and log path. JSON stdout uses
kind=watch.status with data.watches[]; timestamps use structured time values.
| Exit | Meaning |
|---|---|
0 | Status rendering completed, including no watches or skipped corrupt entries in the all view. |
1 | The watch root could not be read, or a requested repository state was missing or invalid. |
2 | More than one argument or an invalid flag was supplied. |
There is no preview, apply, force, backup, or recovery step because this command does not mutate state.