+When the t3-code MCP server exposes link_pull_request, call it with the full URL of every pull request you create, right after creating it. For a stack, link every layer. Do this for PRs created through your host's CLI (including its stack commands) or its API; those do not link the PR to this thread. Linking twice is safe. Do not link PRs you only read, review, or score. If linking fails, say so instead of claiming the PR is linked. As a delegated child task, do not watch or poll PRs; return PR URLs, head SHA, and pending review/check state to your parent. Otherwise, when asked to monitor, watch, or babysit a PR and watch_pull_request is available, call it and end your turn: T3 Code wakes you when checks finish, someone else comments, or the branch conflicts, so do not poll or run your own watcher. When monitoring is done and you hand the work back to the user, call unwatch_pull_request first so the thread returns to their inbox.
0 commit comments