[henrychu04]

Stage 2 of the be1d066 → becf853 upstream sync: upstream main from pingdotgg#25324 (new design on by default) through becf853, 112 commits. Stage 1 was #256.

Carried

• New design on by default (feat(web): new design is on by default pingdotgg/t3code#25324).
• Settings regrouped into focused pages (refactor(web): settings group by concern, with General split into focused pages pingdotgg/t3code#25651), with the fork's Connections page shown as "Environments".
• Thread state at the end of the timeline (feat(web): thread state lives at the end of the timeline, not stacked on the composer pingdotgg/t3code#25401).
• App-level theme, toast and chrome services (refactor(web): root theme, toast and chrome sync start with the app pingdotgg/t3code#25461), chat route commands, and revisioned queries.
• The "could not load" (feat(web): "could not load" screen tells users how to debug it pingdotgg/t3code#25317) and "failed to start" (feat(web): "failed to start" screen helps users recover and report the crash pingdotgg/t3code#25345) screens.
• Fixes: goals, worktree-deleted recovery (fix(server): a thread whose worktree was deleted recovers on the next message pingdotgg/t3code#18359), the PR-sweep cache release, and the Claude MCP-registration retry (fix(server): retry stalled MCP registration for resumed Claude turns pingdotgg/t3code#25372). The retry only runs when MCP servers are configured, which the fork never does.

Cut

• The evals package (feat(evals): shared evals package and an eval for T3 tool-use mistakes pingdotgg/t3code#24635), the multi-account warning (feat(web): warn before adding a second Claude or Codex account pingdotgg/t3code#25475), and the access, browser and devices settings pages.
• Desktop CLI state, telemetry and T3 Connect fixes, docs/user/faq.md, and mobile e2e tooling.
• The failed-to-start screen keeps reload and copyable error details. It drops the desktop update button, the download link, the t3 triage command and the upstream issue link.
• Labs has no Beta (guest links) section.

Adaptations after the merge commit

• GitLab merge request summaries now use upstream's read (perf(source-control): pull request previews read only the pull request pingdotgg/t3code#22583). The fork's batched GraphQL summary is removed. The GitLab files are upstream's again apart from the 6 MiB diff cap, and upstream's auto-merge squash test is back.
• The "open merge requests in T3 Coder" toggle is back on the Diffs page. Upstream defines it in IntegrationsSettings.tsx, which the fork doesn't carry, so the setting openPullRequestLink.ts reads had no UI.
• coder-only.md updated with the seams.

Verification

• All typechecks in AGENTS.md pass, as do pnpm knip:check, pnpm build, and vp fmt --check on the changed files.
• pnpm test:coder passes on the merge commit and again on the final head. Server: 3,188 tests. Web: 3,895 unit and browser tests.
• Section 6 checks: marker counts, lost upstream lines, unused locals, and lines lost even though both sides kept them. Every remaining hit is a cut surface, a listed seam, or code upstream moved.
• Smoke tests with mocks: gateway with the helper, signed assets, and the fake-glab merge request smoke. The MR smoke covers list, summary, detail, diff, checks and filter options; the summary now goes through the detail read with no GraphQL calls.
• The bundled Linux helper boots in a node:24 amd64 container and extracts notebook text.
• Not done: a live Coder workspace check.

🤖 Generated with Claude Code