Bug: Google sign in fails due to invalid redirect URI on Windows

[indishere]

BUG REPORT

OS: Windows
Auth provider: Google
Version: Latest (downloaded today)

Description

When attempting to sign in with Google, T3 Code shows an error saying the current redirect URL does not match an authorized redirect URI.

Error shown:

The current redirect url passed in the sign in or sign up request does not match an authorized redirect URI for this instance.
Review authorized redirect urls for your instance.

The app redirects to:

t3code://app/CLERK-ROUTER/VIRTUAL/sign-up#/settings/general

Screenshot

Attached screenshot shows the full error dialog.

Steps to reproduce

1. Open T3 Code
2. Click Sign in
3. Choose Google authentication
4. Observe redirect URI error

Expected behavior

Google authentication should complete successfully and return to the app.

Actual behavior

Authentication fails because the redirect URI is rejected.

[indishere]

Forgot to attach image*

[fuggysense]

Same error on macOS — third platform affected, and via a different redirect path than the one in the original report.

Environment

• macOS 26.2, arm64 (Apple Silicon)
• T3 Code 0.0.31, installed via brew install --cask t3-code
• Fresh install, first sign-in attempt from Settings

Error

Identical text:

The current redirect url passed in the sign in or sign up request does not match an authorized redirect URI for this instance. Review authorized redirect urls for your instance.

Redirect URI

t3code://app/continue#/settings/genera…

(the tail was cut off in the dialog)

This differs from the t3code://app/CLERK-ROUTER/VIRTUAL/sign-up#/settings/general reported above — so the allowlist gap covers app/continue as well as the virtual sign-up router, not just a single path. Worth checking whether every t3code://app/* callback is registered on the Clerk instance rather than patching them one at a time.

Same root cause as #4815 (Linux AppImage), closed 2026-07-29 — the macOS callback still fails on 0.0.31.

For anyone else landing here: this only blocks T3 Connect. Local providers (Claude Code, Codex, Grok Build) and direct LAN / Tailscale Serve pairing all work fine signed out.