Threads
Schedules and subscriptions
Wake a thread on a schedule, a CI result, a review or a reminder.
A subscription is a rule attached to a thread that wakes it later: on a schedule, at a reminder time, or when something happens on GitHub. A fire never starts a new thread. It adds a short message to the same thread, and the agent reads the saved prompt and acts with everything it already knows.
Ask the thread
There is no form: you ask the agent in plain words and it creates the subscription with its tools. For example:
- "Every weekday at 9:00, check the nightly build and fix what broke."
- "Remind me tomorrow at 14:00 to review the migration."
- "Watch CI on this commit and fix any failing check."
- "When the pull request gets a review, address the comments."
Kinds
| Kind | Wakes the thread |
|---|---|
| Scheduled prompt | On a recurring schedule in your time zone. |
| Reminder | Once, at a set time. |
| GitHub checks | When checks on a commit finish. |
| GitHub review | When a pull request is reviewed. |
| GitHub comments | When a pull request or issue gets comments. |
Schedules repeat at most every five minutes, and the first run is at least five minutes away. A thread has at most one schedule. An agent subscribes to checks and reviews before calling a pull request complete.
See and change them
Thread details → Subscriptions lists a thread's subscriptions, each with its saved prompt and recent deliveries. Pause one with its switch or delete it. Settings → Notifications lists them across threads.
A thread with an active subscription stays Ready to review, since it still has work coming.
Notifications
A subscription turn does not notify you by itself. The agent can tell you about something worth your attention with its notify_owner tool, which follows your notification settings.