ak watch

Use ak watch to discover commands that poll GitHub issues, generate responses through an AgentKit skill, and optionally post comments.

Usage

ak watch

The parent has no positional arguments or command-specific flags. It shows help and performs no GitHub request, agent invocation, state write, or prompt.

Choose a subcommand

Credentials and privacy

Polling and posting execute the local gh CLI and inherit its GitHub authentication and environment. Response generation executes ak run, so the selected skill, runtime, provider credentials, and provider network policy also apply. The issue title, body, author, labels, number, repository, and URL are placed in the agent prompt. Review repository privacy and provider policy before running either start or dry-run.

The default rolling ceiling is 10 successfully recorded posts per hour per repository state. This is a safety bound, not a permission boundary or a review queue. Use least-privilege GitHub credentials and preview filters first.

Output and exit status

Subcommands define their own single-object or streaming JSON contracts. Parent help declares exits 1 for runtime failures, 2 for invalid invocations, and 3 for one-shot rate limiting. The current one-shot implementation handles per-issue rate-limit, agent, and posting errors as stderr log entries and can still exit 0; do not use exit status alone to prove every matched issue was posted.

Related commands

• Preview a watch
• Start posting
• Inspect watch state
• Stop persisted watch state
• Complete ak watch command facts