Watches
Plugins can publish events for resources such as issues, pull requests, and deployments. Junior creates a watch or automation only when asked.
Choose a Watch or Automation
Section titled “Choose a Watch or Automation”- Watch for “watch this” or “tell me when”. Use it when you want temporary, thread-bound updates in the current conversation.
- Event automation for “whenever this happens, do this”. Use it when you want durable automation that stays attached to a Slack channel or DM.
An install can also create a temporary subscription after a successful provider action, or add short event guidance in plugins.ts. That install policy is separate from a user-authored watch or event automation. See the GitHub plugin for a concrete example.
Examples
Section titled “Examples”watch this pull request and tell me when its checks failwhenever an issue is reopened in this repository, summarize why in this channelwhenever a non-draft pull request opens in this repository, review itOptional match values come from the resource type. Junior drops events that do not match before it wakes the agent. Use a match key only when that resource type lists it. For GitHub, is_draft, head_branch, opener_username, opener_email, opener_role, and authors work on pull_request and on repository watches that receive pull request events. head_branch is the branch GitHub sent on the webhook. opener_username is who opened the pull request. On a pull request that Junior opened, it is the GitHub account linked to the person who asked Junior to open it. Junior reads that link when the event arrives, so it also works after the person links GitHub later. People who only asked for updates do not change it. When Junior does not know that person’s GitHub account, the event has no opener, and filters on it do not match. opener_role is the opener’s role on the repository, such as admin, maintain, write, read, or none for most bots. For example, match opener_role: ["read", "triage", "none"] to skip pull requests from people who can push. authors is a list of the GitHub logins of the commit authors and Co-authored-by people, bots included. A match value matches when the list includes it, so match authors: "octocat" for pull requests that octocat wrote or co-wrote. Junior loads the opener role and the authors only when a filter uses them or an event matches, and the agent sees them in the event. Check suites with no pull request still publish to the repository, so you can watch builds on main. For Linear, team_key works on issue and team watches that receive issue events. If a listed value is missing on the event, Junior does not match.
Each event also carries the values of its scope, and each value is a match key. For GitHub, events carry repo, and pull_request, issue, commit_sha, deployment_id, or tag when the event has one. A check suite with no pull request has no pull_request. For Sentry, events carry projects, and issue events also carry issue_id. projects is a list: an issue has one project, and a metric alert has the projects of its rule. Sentry events have no org value, because one Sentry integration belongs to one org. For Vercel, events carry project_id and deployment_id. For Linear, issue events carry issue_identifier and team_key. The values use the same case as identifiers. GitHub and Sentry values are lowercase, Vercel ids keep their case, and Linear values are uppercase. A GitHub tag is the release tag as GitHub sent it, with only ASCII letters in lowercase, such as release/1.0.
Events With No Reply
Section titled “Events With No Reply”Some watch events need nobody’s attention, such as a routine CI fix that worked or bot review feedback that Junior handled. For these events, Junior ends the turn with no reply and an optional note. It posts nothing in Slack and adds no reply in the web view. The web view puts the event and its tool calls in one row that you can open, and the note is the input of the noReply call.
See and Cancel Watches
Section titled “See and Cancel Watches”The details panel of a conversation lists its active watches and timers. Each row shows what Junior will do and when the watch fires or expires. Hover over the time to see the exact time. A participant can cancel a watch there. Junior gets no message about the cancel. The watch does not wake it again.
Limits
Section titled “Limits”- Watches default to 14 days and cannot exceed 30 days.
- Event data cannot change conversation visibility or credential access.
- App guidance cannot grant credentials, expand an instruction, or bypass action review.
- Duplicate provider deliveries should not create duplicate work.
- Events currently require single-workspace Slack mode.
Each plugin page lists its supported resources, events, and webhook setup.
Next Step
Section titled “Next Step”Choose a provider from Plugins, or read Automations for durable automation.