[Bug] Desktop app crashes on launch after macOS 27 upgrade (DesktopLocalEnvironmentAuthSessionBootstrapError)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, typescript
- Domain
- authentication, desktop
Research direction
Start in apps/desktop by tracing the primary local environment bootstrap from the renderer beforeLoad path through the main-process /oauth/token exchange. Inspect how DesktopLocalEnvironmentAuthSessionBootstrapError reaches RootRouteErrorView, then reproduce with pnpm build:desktop && pnpm start:desktop. Done means a transient loopback failure is recovered from and the app reaches chat or pairing UI instead of crashing.
Written by the indexing model from the issue text.
Description
Area
apps/desktop
Steps to reproduce
- On macOS 27 (Build 26A428), build and launch the T3 Code desktop app (
pnpm build:desktop && pnpm start:desktop). - The app attempts to bootstrap the primary local environment on launch.
- The main-process
/oauth/tokenexchange over loopback hits a transient failure (connection reset / brief 503 while the backend settles — newly common after the macOS 27 upgrade). - The renderer crashes to the root error view during
beforeLoad.
Expected behavior
The app boots to the chat view (or the pairing UI if unauthenticated), riding out the transient loopback failure.
Actual behavior
The app crashes to RootRouteErrorView with PrimaryEnvironmentRequestError caused by DesktopLocalEnvironmentAuthSessionBootstrapError: Failed to create the local desktop bearer session. No recovery path; relaunch may work if the transient condition has cleared.
Impact
Blocks work completely
Version or commit
main (pre-fix)
Environment
macOS 27.0 (Build 26A428), desktop app, Node v23.10.0
Logs or stack traces
PrimaryEnvironmentRequestError
← DesktopLocalEnvironmentAuthSessionBootstrapError: Failed to create the local desktop bearer session
← RemoteEnvironmentAuthUndeclaredStatusError (503) | RemoteEnvironmentAuthFetchError | TypeError
Workaround
Relaunch after the transient condition clears. No in-app recovery.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 201
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pingdotgg/t3code#16096 · 1 comment ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pingdotgg/t3code#16090 · 2 comments ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
pingdotgg/t3code#15954 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
area:docs bug triage:confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Cotal-AI/Cotal#2875 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/models.dev#8862 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(data-lake): wizard source step still previews the local slug, not the server-disambiguated oneOpendata-lake
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ready-for-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
konflux-ci/konflux-ui#1596 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day