Summary
The create_watch tool accepts a check parameter for a registered plugin verifier, but the GitHub plugin currently doesn't expose any verifiers (e.g. github:issue_updated, github:issue_comments, github:issue_activity). Attempts to use GitHub-related verifier names all fail with a check_args validation error, suggesting the verifier isn't recognized at all.
Motivation
Watches are a core agent capability — they let the agent monitor external state changes and act on them. Without GitHub verifiers, agents can't:
- Watch an issue for triage (label changes, comments, assignees)
- Watch a PR for CI status changes
- Watch a repo for new releases or branches
- Trigger follow-up actions when GitHub state changes
This is a gap between the watch system's design and the GitHub plugin's capabilities.
Proposed Verifiers
Suggested verifier names and what they'd check:
| Verifier |
Checks |
github:issue_updated |
Issue labels, comments, status, assignees changed |
github:issue_comments |
New comments on an issue/PR |
github:pr_status |
PR CI checks passed/failed |
github:pr_merged |
PR merged or closed |
github:release_published |
New release published to repo |
Each would take check_args like {"repo": "owner/name", "number": 123} or {"repo": "owner/name"} depending on scope.
Acceptance Criteria
Notes
- The GitHub plugin already has tools like
github_get_issue, github_get_pr, github_ci_runs — the verifiers would wrap these with polling + change detection.
- This is a plugin-level feature, not a core agent change.
Summary
The
create_watchtool accepts acheckparameter for a registered plugin verifier, but the GitHub plugin currently doesn't expose any verifiers (e.g.github:issue_updated,github:issue_comments,github:issue_activity). Attempts to use GitHub-related verifier names all fail with acheck_argsvalidation error, suggesting the verifier isn't recognized at all.Motivation
Watches are a core agent capability — they let the agent monitor external state changes and act on them. Without GitHub verifiers, agents can't:
This is a gap between the watch system's design and the GitHub plugin's capabilities.
Proposed Verifiers
Suggested verifier names and what they'd check:
github:issue_updatedgithub:issue_commentsgithub:pr_statusgithub:pr_mergedgithub:release_publishedEach would take
check_argslike{"repo": "owner/name", "number": 123}or{"repo": "owner/name"}depending on scope.Acceptance Criteria
github:issue_updatedandgithub:pr_statusare registered as usable verifiers forcreate_watchrun_promptin-session when a change is detectedNotes
github_get_issue,github_get_pr,github_ci_runs— the verifiers would wrap these with polling + change detection.