Skip to content

[Bug]: watch_pull_request's description still omits the merge wake, so agents keep working around it #39726

Closed

Description

@paul-cch

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

  1. Use a build that includes fix(server): watched PRs wake the agent when they merge #26271, such as 0.1.11-nightly.20261120.4979.
  2. Ask an agent with the T3 Code tools what watch_pull_request wakes it for, or ask it to take a PR through auto-merge and then do post-merge work.
  3. The agent answers from the tool description, which still reads: "T3 wakes you on failed checks, passed required checks, new comments or reviews, or conflicts." It concludes that a merge won't wake it.

Expected behavior

The description lists the wake that #26271 added. For example: "…new comments or reviews, conflicts, or the PR merging or closing, unless you merged or closed it yourself with the host's CLI."

Actual behavior

Agents follow the description, which now contradicts the behavior and the user guide.

  • A wrong standing instruction. After fix(server): watched PRs wake the agent when they merge #26271 merged, an agent in our setup wrote a standing instruction for other agents saying "a merge or close ends the watch without waking the thread". It told them to poll gh pr view in the background instead. It ran on a build that already had the merge wake.
  • Unnecessary workarounds. Other agents tell the user they'll poll, or ask the user to check whether the PR merged. That costs turns and API reads, and it cuts against the injected guidance not to run your own watcher.

Impact

#26271 says the descriptions were left unchanged "so the agent context budget stays flat; the wake itself tells the agent the watch ended." That works once the wake has arrived. But agents plan, and promise users follow-up, before any wake arrives, and the description is the only contract they see at that point. The fix's benefit is lost exactly where agents decide whether to keep a turn open or start their own watcher. The change costs about ten words.

For scale, before #26271 the local state databases on three of our hosts held no merge wake at all. On one host, 31 watched PRs merged without a wake. That matches #25160, and it's the habit agents are still carrying.

Version or commit

Server 0.1.11-nightly.20261120.4979, tag commit 59651c1, which contains 7dceb76 from #26271. The description is at apps/server/src/mcp/toolkits/pullRequests/tools.ts on main, in WatchPullRequestTool.

Environment

Linux, served by t3 serve. Claude Code provider (Claude Opus 5.5) and Codex provider (GPT-6.1 Sol).

Logs or stack traces

None. This is a wording mismatch between the tool description and docs/user/source-control.md, which says: "When the pull request merges or closes, watching ends, and the agent is woken once unless it merged or closed the pull request itself with the host's CLI."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions