fix: enable T3 Connect in the T3 Code web frontend #6

Merged

marti merged 1 commit from fix/t3code-connect-jwt-template into main

2026-10-19 14:33:02 +02:00

marti commented

2026-10-19 14:30:06 +02:00

Owner

Problem

After #5, T3 Code still showed no T3 Connect section under Settings > Connections.

The web frontend gates every T3 Connect surface on hasCloudPublicConfig(), which needs three build-time values: VITE_CLERK_PUBLISHABLE_KEY, VITE_T3CODE_RELAY_URL and VITE_CLERK_JWT_TEMPLATE. llm-agents sets T3CODE_RELAY_URL, T3CODE_CLERK_PUBLISHABLE_KEY and T3CODE_CLERK_CLI_OAUTH_CLIENT_ID, but not T3CODE_CLERK_JWT_TEMPLATE, so the built bundle had clerkJwtTemplate: "" and the whole section was hidden.

Fix

Add T3CODE_CLERK_JWT_TEMPLATE = "t3-relay" to the t3code-unwrapped override's env. t3-relay is the production value from upstream's .env.example, which states these are the same public identifiers baked into official release builds.

Testing

nix flake check passes.
Built the desktop output; the web bundle now has clerkJwtTemplate:ky(`t3-relay`). The server and desktop main process do not read the template.
Not yet tested: T3 Connect sign-in from the running app.

Worth reporting upstream to numtide/llm-agents.nix together with the URL handler issue from #5.

🤖 Generated with Claude Code

## Problem After #5, T3 Code still showed no T3 Connect section under Settings > Connections. The web frontend gates every T3 Connect surface on `hasCloudPublicConfig()`, which needs three build-time values: `VITE_CLERK_PUBLISHABLE_KEY`, `VITE_T3CODE_RELAY_URL` and `VITE_CLERK_JWT_TEMPLATE`. llm-agents sets `T3CODE_RELAY_URL`, `T3CODE_CLERK_PUBLISHABLE_KEY` and `T3CODE_CLERK_CLI_OAUTH_CLIENT_ID`, but not `T3CODE_CLERK_JWT_TEMPLATE`, so the built bundle had `clerkJwtTemplate: ""` and the whole section was hidden. ## Fix Add `T3CODE_CLERK_JWT_TEMPLATE = "t3-relay"` to the `t3code-unwrapped` override's `env`. `t3-relay` is the production value from upstream's `.env.example`, which states these are the same public identifiers baked into official release builds. ## Testing - `nix flake check` passes. - Built the desktop output; the web bundle now has ``clerkJwtTemplate:ky(`t3-relay`)``. The server and desktop main process do not read the template. - Not yet tested: T3 Connect sign-in from the running app. Worth reporting upstream to numtide/llm-agents.nix together with the URL handler issue from #5. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

marti added 1 commit

2026-10-19 14:30:06 +02:00

fix: enable T3 Connect in the T3 Code web frontend 9c37241dee

The frontend shows T3 Connect only when the Clerk JWT template is built in
next to the publishable key and relay URL. llm-agents sets the other two but
not T3CODE_CLERK_JWT_TEMPLATE, so the section never appeared. Set it to
t3-relay, the production value from upstream's .env.example.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

marti merged commit ef6ea93160 into main

2026-10-19 14:33:02 +02:00

marti referenced this pull request from a commit

2026-10-19 14:33:04 +02:00

Merge pull request 'fix: enable T3 Connect in the T3 Code web frontend' (#6) from fix/t3code-connect-jwt-template into main

marti referenced this pull request

2026-10-19 14:47:14 +02:00

chore: update llm-agents for T3 Code 0.1.0 #7