Skip to content

Update T3 contract to 59651c1 - #93

Merged
pmwoz merged 1 commit into
mainfrom
t3/t3-contract-59651c1
Nov 20, 2026
Merged

pmwoz merged 1 commit into
mainfrom
t3/t3-contract-59651c1

Conversation

@pmwoz

@pmwoz pmwoz commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

Moves the T3 pin from 082bc2c to 59651c1, the build tagged v0.1.11-nightly.20261120.4979 that sessions on this machine run. Nine tools were added and none removed. The adapter changed, so the plugin goes to 0.17.1, on top of #92.

T3 commits

  • 37f8a53 feat(server): agents land a GitHub stack in one merge (#38973)
  • f7041fa feat(server): agents read failing CI logs and re-run checks through MCP tools (#26752)
  • 5d05902 feat(server): agents read, open, update, respond to, and merge PRs through MCP tools (#26751)
  • 28d96a2 fix(server): a PR watch the agent owns keeps its thread working until the PR merges (#38926)
  • 7dceb76 fix(server): watched PRs wake the agent when they merge (#26271)

Tools added: pull_request_read, pull_request_list, pull_request_create, pull_request_update, pull_request_respond, pull_request_review, pull_request_merge, ci_logs, ci_rerun. T3 lists them whenever it can reach the thread's forge, including in delegated children.

Breaks a mapping

The injected <pull_request_linking> block now says: "When pull_request_* tools are listed, use them, not gh or cafe, to read, list, open, edit, review, reply on, close, or merge PRs, and ci_logs and ci_rerun for their checks. pull_request_create links for you." The adapter said "T3 has no PR-creation tool" and sent agents to gh or origin. Fixed in t3-adapter.md, Pull requests section:

  • New PR tools bullet: when the tools are listed, they replace gh and origin for every PR and check operation a playbook names. Without them, the playbooks' forge commands apply.
  • Opening a PR: pull_request_create is the run's PR tool, called with draft: false and base for a stacked layer. It opens from the calling thread's pushed branch and links it to that thread. The forge fallback and the root-links-every-PR rule stay.
  • /loop around a PR: the fallback read is pull_request_read before origin or gh pr view.

Opportunities

Adopted in a follow-up PR.

  • pull_request_merge with stack: true lands a PR and every open layer below it in one merge. The shipping playbook's step 4 (land bottom-up, one PR at a time) and autopilot-stack could use it.
  • pull_request_merge with auto: true merges once required checks pass, and expectedHeadSha refuses a moved head. The shipping playbook could merge on green without a watch round.
  • pull_request_respond replies to and resolves review threads by id. Babysit's Bugbot triage could dismiss noise in the thread and resolve it.
  • pull_request_review submits a verdict with up to 50 line comments. A review lane that posts findings to the PR, such as interrogate's, could use it.
  • ci_logs returns the failing checks' log tails, and ci_rerun re-runs one named check. Babysit's CI step could rerun a check it proves flaky.

Irrelevant to the skills

3 changes: watched PRs wake the agent on merge, an owned PR watch keeps its thread working until merge, and a shared commandIndicatesFailure helper.

Checks

bun run check, bun test tools (40 pass), and bun run typecheck pass on the rebased head.

@pmwoz
pmwoz force-pushed the t3/t3-contract-59651c1 branch from 21ea7c9 to b034bf0 Compare November 20, 2026 08:11
@pmwoz
pmwoz merged commit d87f54e into main Nov 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant