The Link a machine dialog and the link cards on web and mobile say to make a pairing code under Settings → Connections → Create link. Connections is a sidebar group with two pages, Environments and Sharing & access, so the path stops one level short. Environments (/settings/connections), the first page in that group and the one this dialog lives on, has no Create link button. The button is in the Authorized clients header on Sharing & access (/settings/access). Fixes #27688.
The copy now points at the pages that hold each control:
| 1 | Pairing code hint (web settings dialog, web link card, mobile link card) |
| 2 | -Settings → Connections → Create link |
| 3 | +Settings → Sharing & access → Authorized clients → Create link |
| 4 | |
| 5 | Revoke hints (dialog headers, Forget confirm, pairing placeholder, t3 environment link/unlink) |
| 6 | -in that machine's Connections |
| 7 | +in that machine's Sharing & access (under Authorized clients where the sentence has room) |
| 8 | |
| 9 | "Already linked" hint (web and mobile link card) |
| 10 | -change its access in Settings → Connections |
| 11 | +change its access in Settings → Environments |
PeerLinks.link registers the linking machine on the other machine as an OAuth client named T3 Code · <label>. EnvironmentAuth.listClientSessions returns that session, and Sharing & access lists and revokes it under Authorized clients. So the revoke hints belonged on Sharing & access as well. The Linked environments section, where a link's access is changed by linking again, is rendered by ConnectionsSettings on the Environments page.
The t3 pair there hint stays. One more stale string remains on purpose: the MCP t3_environment_unlink description in apps/server/src/mcp/toolkits/orchestrator/tools.ts also says "Connections". It is text a model reads, and changing it would mean running the paid mcp-tool-use eval, so it is left for a separate change.
This is a copy-only fix for the bug in #27688. It changes no behavior.
vp run check:changed upstream/main passed: format, lint, knip, graphql, typecheck of 5 packages, the test beside the change, and the React compiler check.
After the change, grep -rn "Connections" over the four touched files finds nothing.
Ran base (1da41f9) and head dev servers side by side, saved each as an environment in the other with a pairing code that lacks access:write, turned on Linked environments in Labs, and opened Link with that machine selected. That is the state where the dialog asks for a code.
Before: Link an environment dialog, before After: Link an environment dialog, after
Where the new path leads, on the other machine. Create link sits in the Authorized clients header on Sharing & access:
Not captured: the web link card and the mobile link card. Both need a link request that an agent posts in a thread. They render the same hint text as the dialog above, changed in the same way.
Posted by Claude Code (claude-opus-5-5) via T3 Code triage.
Fixes pingdotgg/t3code#27688
Verdict: Approved at 52729e0
Macroscope's review found this PR approvable — Updates pairing and revocation instructions to use the current settings names across web, mobile, and CLI. The changes are text-only and leave access controls, defaults, and linking behavior unchanged.
You can add or adjust custom eligibility rules. Learn more.
No actionable comments were generated in the recent review.
The linked-environment instructions in web, mobile, and CLI now refer to Sharing & access and Authorized clients for link creation, access changes, and revocation.
Changes: Linked environment guidance
| Layer / File(s) | Summary |
|---|---|
Update linked-environment navigation guidance apps/web/src/components/settings/LinkedEnvironmentsSettings.tsx, apps/web/src/components/chat/LinkRequestCard.tsx, apps/mobile/src/features/threads/LinkRequestCard.tsx, apps/server/src/cli/environment.ts | Instructions identify Sharing & access and Authorized clients for creating, finding, changing access to, and revoking links. The unlink operation and its no-match message are unchanged. |
Estimated code review effort: 2 (Simple) | ~8 minutes
Change: Bug fix · Severity of issue fixed: Low
Suggested reviewers: juliusmarminge
52729The copy-only navigation updates are consistent with the current web, mobile, and CLI settings destinations.
| Check name | Status | Explanation |
|---|---|---|
| Title check | Passed | The title clearly identifies the main change: updating pairing copy to reference Sharing & access. Although mobile and related revoke guidance are not named, the title is concise and accurately descri… |
| Linked Issues check | Passed | The changes satisfy the coding requirements in [#27688]. The web dialog, web link card, and mobile link card now direct pairing-code users to `Settings → Sharing & access → Authorized clients → Create… |
| Out of Scope Changes check | Passed | All changed files support [#27688]. The web and mobile copy fixes address the reported settings paths. The CLI description and message fixes address the same stale revoke guidance identified by the is… |
| Description check | Passed | The description covers the problem, changes across web, mobile, and CLI, scope, and focused verification. It includes screenshots for the dialog, reports test results, and identifies the MCP unlink te… |
Explanation
The title clearly identifies the main change: updating pairing copy to reference Sharing & access. Although mobile and related revoke guidance are not named, the title is concise and accurately describes the primary fix.
Explanation
The changes satisfy the coding requirements in [#27688]. The web dialog, web link card, and mobile link card now direct pairing-code users to Settings → Sharing & access → Authorized clients → Create link. Revoke guidance now names Sharing & access, with Authorized clients included where space permits. Existing-link guidance now names Settings → Environments. The t3 environment link and t3 environment unlink CLI descriptions and unlink success message also use the corrected location. The diff changes copy only and does not alter linking behavior.
Explanation
All changed files support [#27688]. The web and mobile copy fixes address the reported settings paths. The CLI description and message fixes address the same stale revoke guidance identified by the issue. No unrelated behavior or unrelated product area changed. The unchanged MCP description is an explicitly deferred string and does not make the present changes out of scope.
Explanation
The description covers the problem, changes across web, mobile, and CLI, scope, and focused verification. It includes screenshots for the dialog, reports test results, and identifies the MCP unlink text left unchanged for a separate change.
59e13d59-f059-4c6b-b1ab-75c763191888Reviewing files that changed from the base of the PR and between 1da41f949950bda57f45dc73effb7543037c844f and 52729e0cb037ef273da86425cacf6fbba560b42f.
apps/mobile/src/features/threads/LinkRequestCard.tsxapps/server/src/cli/environment.tsapps/web/src/components/chat/LinkRequestCard.tsxapps/web/src/components/settings/LinkedEnvironmentsSettings.tsxIncluded review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
Added 1 commit
Note
Written by gpt-6.1-sol on behalf of Maria
verified unchanged at 7b6b90f0ad0d2716ae3265a25b99f005be126575 on this linux boat vm, using repo playwright 1.60.0 and /usr/bin/google-chrome.
github/main (5fe18d79ac) in a separate worktree, then stopped its dev server before starting the exact pr head with isolated state. one dev runner at a time.gpt-6.1-sol turns on both revisions. the resulting link-request cards show the old and corrected pairing paths. the settings link dialog also shows the corrected revoke guidance and placeholder.T3 Code · … oauth session. the existing-link card points to settings → environments. the forget confirmation points to sharing & access.current github checks: 21 successful, 8 skipped, no failures or pending checks. no source changes, commits, or pushes were needed. automated checks were not rerun.
main settings dialog:
main settings link dialog with stale connections guidance
pr settings dialog:
pr settings link dialog with sharing and access guidance
main codex-generated link card:
main codex link card with stale create-link path
pr codex-generated link card, same form state:
pr codex link card with corrected create-link path
settings navigation, pairing-link creation, pairing-link revocation, and client revocation:
real settings creation and revocation flow
media rendering limitation: the four screenshots render on github. github does not embed the mp4 with the requested image markdown, and git.cafe renders external media as links. the uploaded mp4 was opened in t3's rendered browser player, played to the end, and successfully sought.
native ios/android and the electron shell were not exercised on this linux browser setup. windows/macos, relay/tailscale/tunnel connections, and providers other than codex were not exercised. the older installed peer could not complete a link because of its version guard; the same-head peer completed it. no claim is made about older versions having the new settings names.