You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b976b00
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): an agent's own merge or close ends its watch without a wake
The merge wake also fired when the thread's own agent had just merged the pull
request with its host's CLI, costing a turn to tell it what it already knew.
The watch reactor now follows the thread's merge and close commands: a pull
request that ends while one runs, or since one ended after the last read that
found it open, ends its watch quietly, and the command's end reads the thread's
watches at once. A merge that lands later, as with `--auto`, still wakes.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: docs/user/source-control.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -332,8 +332,8 @@ conflict. On github.com it also wakes the agent, with GitHub's reason, when the
332
332
the pull request without merging it. Threads in a project that watch the same pull request share one check. On GitHub, a check
333
333
first asks whether anything changed and reads the pull request only when it did, which keeps
334
334
watching inside GitHub's rate limit. Comments from your own account do not wake it. When the pull
335
-
request merges or closes, the agent is woken once and watching ends; a reopened pull request needs a
336
-
new watch. Watching also ends after 10 wakes in a row that bring only comments, after 8
335
+
request merges or closes, watching ends, and the agent is woken once unless it merged or closed the
336
+
pull request itself with the host's CLI. A reopened pull request needs a new watch. Watching also ends after 10 wakes in a row that bring only comments, after 8
337
337
failed reads in a row, or when you press Stop on the thread. A rate limit only pauses watching.
338
338
Settling or archiving a thread also ends all its watches. Unsettle the thread before starting a new
339
339
watch. Watching a pull request again does not repeat check or conflict news its last
0 commit comments