Snooze a thread until its pull request changes

[Zheckan]

Summary

Add Until pull request changes to the snooze menu. The thread stays snoozed until its linked pull request gets a review, a comment, a check result, or a merge conflict. Then it comes back to the sidebar with a note that says what changed. The agent does not run.

Problem

I contribute to open-source projects where a review can take a week or a month. I open a pull request from a thread, and then the thread waits. After three idle days, auto-settle moves it to the settled shelf. When a reviewer finally comments, nothing in T3 Code tells me. I hear about it from GitHub, then search the settled shelf for the thread where I wrote the change, so I can make the fix with the same context.

Snoozing for a fixed time doesn't help much. I have to guess when the reviewer will get to it. If I guess short, the thread comes back with nothing new and I snooze it again. If I guess long, the review sits unseen until the snooze ends.

Proposal

The option appears for threads that have a linked open pull request.

1. The thread moves to Snoozed, like any other snooze.
2. The server checks the pull request on the same schedule as watch_pull_request and reuses its reads.
3. When something changes, the server wakes the thread and adds a timeline notification that says what changed. The agent does not start a turn.

A change is anything the watch already reports: a check fails, the required checks pass, someone other than me comments or reviews, or the branch starts to conflict. My own pushes and comments don't count.

This is a snooze and not a settle on purpose. Settled means the work is done, and settling a thread ends its pull request watches. A snoozed thread also doesn't auto-settle while it waits.

Wake thread works as it does today and also stops the check. The option works on web, desktop, and mobile, and on every host that watch_pull_request supports.

Why watch_pull_request doesn't fit

The closest option today is to ask the agent to call watch_pull_request, then snooze the thread for a long time. When the watch sees a change, it starts an agent turn, and the thread comes back after that run completes.

That hands the review to the agent. It reads the comments and starts acting on them before I have seen them. I want to read the review myself first, decide what to change, and then tell the agent what to do. Each check result and comment also costs an agent turn, and the watch stops after 10 comment-only wakes in a row.

Related

• Auto-snooze green PRs from the PR watch tool, opt-in setting #15303 snoozes a thread automatically once its watched pull request goes green. This proposal wakes a thread I snoozed myself when its pull request changes.
• Snooze a running thread until its run ends #14819 asks for a snooze that ends when a running thread's run ends. It also wakes on an event instead of a time, but on a different event.

[ashx-j]

This would be useful to me. Could it also cover replies on merged PRs and GitHub discussions?

For example, I just used an agent in T3 to comment on a merged PR with a feature suggestion. I'd like to snooze that T3 thread until someone responds, then have it return to my inbox with the new comment and a link. The agent wouldn't need to run or reply automatically.

The same applies when an agent posts in a GitHub discussion. Once we've sent the message, there's nothing for me to do until someone responds, and a fixed snooze time means guessing when that will happen.

An option like “Snooze until someone responds” would fit this well. Would that fit the scope of this proposal, or should it be a separate discussion?

---

Sent by gpt-6-astra, responding on behalf of ashx-j.