main: 5fe18d79ac (github/main)
pr: 7b6b90f0ad0d2716ae3265a25b99f005be126575
Linux, /usr/bin/google-chrome, Playwright 1.60.0 from repo dependencies.
main dev: server 16733, web 8693. Stopped before PR dev.
PR dev: isolated /home/user/t3code/.t3, server 13773, web 5733.
Standalone peer runtime at the same PR head: port 18773, isolated /home/user/pr27692-peer. No second dev runner or Vite instance.

UI-created project and thread, real Codex gpt-6.1-sol turn on main and PR:
- t3_environment_link produced the actual link-request card.
- Main card: Settings → Connections → Create link.
- PR card: Settings → Sharing & access → Authorized clients → Create link.
- Main and PR settings link dialogs show old/new revoke guidance and pairing placeholder respectively.
- Existing-link card: change its access in Settings → Environments.
- Forget confirmation: revoke T3 Code session in peer's Sharing & access.

Successful same-version peer linking via the Codex card:
$ node apps/server/src/bin.ts environment list --base-dir /home/user/t3code/.t3 --json
[{"environmentId":"dd987c5f-007b-49d6-866d-89b0c981ba25","urls":["http://127.0.0.1:18773"],"access":"approval-required","status":"reachable","lastError":null}]
$ node apps/server/src/bin.ts auth session list --base-dir /home/user/pr27692-peer --json
Peer lists an mcp-client session named "T3 Code · box-node-b53f1c84e1dabc44", with orchestration:read and orchestration:operate.

UI on PR's Sharing & access → Authorized clients:
- Created a pairing link named pr27692-proof.
- Copied its code with the actual Copy code button and paired a separate browser context.
- Authorized clients changed from 1 to 2, listing pr27692-proof.
- Created and revoked a second pairing link, pr27692-recording.
- Revoked pr27692-proof. Authorized clients returned to 1.

$ node apps/server/src/bin.ts environment link --help
Link another T3 Code environment, so agents here can work there. It shows up there under Authorized clients in Settings → Sharing & access, where it can be revoked.
$ node apps/server/src/bin.ts environment unlink --help
Forget a linked environment here. Revoke it in that environment's Sharing & access to end its session there too.
$ node apps/server/src/bin.ts environment unlink --base-dir /home/user/t3code/.t3 dd987c5f-007b-49d6-866d-89b0c981ba25
Forgot dd987c5f-007b-49d6-866d-89b0c981ba25. Revoke it in that environment's Sharing & access to end its session there.
Peer still listed the mcp-client session after local unlink, matching the guidance.
POST http://127.0.0.1:18773/api/auth/clients/revoke (authenticated): 200 {"revoked":true}
Peer mcp-client session absent after revocation.

Neighboring guards exercised:
- Installed 0.1.2 peer rejected because it cannot preserve linked-agent limits.
- Same-version peer rejected while Linked environments was off; enabling it via Settings → Labs allowed linking.

GitHub checks on exact head: 21 SUCCESS, 8 SKIPPED, 0 failures or pending.
No source changes, commits, or pushes. No automated checks rerun.
Unverified: native iOS/Android, Electron shell, Windows/macOS, relay/Tailscale/tunnel and other providers.