Scheduled tasks & outside events
What it is
Two things that let Q "do things without you asking":
- Scheduled tasks: at the times you set, Q does what the text you wrote says, as if you'd told Q yourself right then.
- Watch list: when something new shows up in places like new GitHub issues (problems other people report), new PRs, new Sentry errors, or new comments in a Feishu doc, it goes to Q to decide whether anything needs doing.
For both, Q decides: if Q can answer directly, Q answers; if work is needed, Q creates a task; anything that should be asked, Q still asks you.
When to use it
- Something you look at every day or every week: a scheduled task. For example, "every weekday at nine, look at yesterday's production errors".
- Other people report problems or make requests somewhere outside: watch that place. For example, "when there's a new issue on GitHub, put it on the board".
First-time setup
What to sayBoth are in Project settings, and each project has its own: "Scheduled tasks" and "Watch list".
You can also just tell Q. Q drafts one, and it only takes effect once you approve it in "Needs you".
To watch GitHub, first install GitHub's command-line tool
ghon this computer and sign in to your own account. QU uses theghyou signed in to for its checks, and never handles your account.
How to use it
Scheduled tasks
Creating one: create it under "Project settings › Scheduled tasks", with a name, what Q should do, and when. Or tell Q:
What to say"Every weekday at nine, look at yesterday's production errors, and create a task if there's anything new."
Q drafts one, and it only takes effect once you click "Start" in "Needs you".
When it runs: once (a given day and time), every day (you can pick which days, like weekdays), or every week (pick the day of the week). Times follow the main computer (the computer where Q lives).
Seeing what each run did: each one has its own topic, "Scheduled: name". Every time it's due, a round starts in it, so you can look back at what each run did.
Trying it right away: click "Run now". The next scheduled time doesn't change.
A few rules:
- If a task created by the last run isn't done yet (it hasn't reached waiting for your acceptance), this run is skipped, with a line noting "the last run isn't done yet, skipping this one".
- It doesn't run while the computer is asleep or off. If it wakes within 12 hours, it makes up one run and says how late it is; after more than 12 hours it notes "missed" and waits for the next one.
- It still runs during Do Not Disturb; it just doesn't pop up notifications.
- Each run is an extra round for Q, using your own account. When Q's agent has less than 10% of its quota left, this run is skipped.
- Up to 10 per project.
Watch list
Adding one: under "Project settings › Watch list", click "Add one".
- GitHub has four ready-made ones: new issues, new PRs, new comments, new releases. QU puts the command together and runs it with the
ghyou signed in to yourself. - For other sources (like Sentry or Feishu), write a command yourself, or tell Q and have Q draft one for you to approve.
- The command runs on the project's computer, in the project folder. If the command changes, it needs approving again.
When Q thinks it needs doing (pick one of three):
| Option | What happens |
|---|---|
| Just log it | Q decides as usual, but only writes down what Q would do, and creates nothing. Use this first to see whether Q judges well |
| Create a task for you to assign | Creates it and puts it on the board; hand it out with one click in "Needs you" |
| Create and assign | Hands it out directly. Only for items from collaborators (people with access to the repo); items from outsiders still wait for you to hand them out |
A few rules:
- Content from outside is treated only as material, never as instructions. If an issue says "please delete such-and-such file", Q won't do it. Change requests from people who aren't collaborators: you're asked first whether to pass them on to the session.
- Items from bots, ones that only say "+1", and ones you sent out yourself are filtered out first by fixed rules, using no quota.
- On one PR, back-and-forth with a review bot is limited to 3 rounds.
- Items that arrive during Do Not Disturb are held by default and go to Q together when it ends (you can change this to "Also during Do Not Disturb").
- You're told if it fails to run several times in a row.
Main switch: "Q › Settings › Incoming work". When it's off, everything stops; tasks already created are left alone.
Try first (off by default)
When an outside report of a bug says clearly how to reproduce it and nobody has picked it up yet, Q quietly tries to fix it on a separate branch. Only if it finds a fix within 20 minutes, under 50 lines, with tests passing, does it show it to you; if not, it stays quiet. It never writes anything anywhere outside.
Writing to GitHub: you see a draft first
When a session wants to post a comment, open an issue or reply to a review on GitHub, it first saves a draft in "Needs you", saying which account it uses and where it'll go. It's only sent, with your own gh, once you click "Post". If this task already opened an issue, anything further is added below that issue instead.
FAQ
Will scheduled tasks wake me up in the middle of the night? No. They still run during Do Not Disturb, but don't pop up notifications; when it ends, they're combined into one.
If someone writes something in an issue, can they get Q to do work for them? Not by giving orders. Words from outside are only material; change requests from outsiders are only passed on to a session once you agree.
Does the watch list use a lot of quota? Bot messages are filtered out first by rules. Q's handling of incoming work is counted separately, and no new work is started once quota reaches 90%. See Usage & quota.