fix(web): send Connect sign-up back to the app instead of a 404

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.

[Rishet11]

What Changed

Signing in to T3 Connect from the browser worked if you already had an account. Choosing "Use a fresh account" and signing up dropped you on a 404 instead of returning to the app. The account was created, but you were left on a dead page.

Clerk uses two separate redirect targets: forceRedirectUrl after a sign-in, and signUpForceRedirectUrl after a sign-up. resolveClerkSignInProps only set the first one on the web, so sign-up fell back to Clerk's dashboard-configured default, which is a route this app does not serve.

The web branch now sets both, so a new account lands back where the user started.

Why

The Electron branch of this same function already sets both keys to the same URL, and ClerkSignInProps already declares signUpForceRedirectUrl. Only the web branch was missing it. This makes the two consistent rather than introducing a new idea about where sign-up should go.

Two things I checked while making it:

• Should sign-up go somewhere other than sign-in? Electron already sends both to the same place, so same-destination is the behaviour this codebase already chose.
• Should the web href be normalised first, like Electron does? The Electron branch strips the pathname because, per its comment, "Electron routes through the hash", which does not apply in a browser. More to the point, sign-in on the web already passes this exact raw href and returns correctly today, so reusing it for sign-up carries no risk that sign-in is not already carrying.

All three callers (useT3ConnectAuthPrompt.tsx, and ConnectCliAuthSurface.tsx in two places) go through this one function, so they are all covered.

npx t3 connect from the CLI is unaffected either way, which is why that was a workaround.

UI Changes

n/a - no visual change. Sign-up returns to the app rather than a 404.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a)
• I included a video for animation/interaction changes (n/a)

Verification

vp test run apps/web/src/components/clerk/authRedirect.test.ts # 3 passed
vp run --filter @t3tools/web typecheck # exit 0, no errors
vp lint apps/web/src/components/clerk/authRedirect.ts apps/web/src/components/clerk/authRedirect.test.ts
vp fmt --check <same two files>

Reverting the source line makes the web test fail, so it covers the changed behaviour.

Fixes#6302

Implemented with Claude Opus 5 via Claude Code.

---

Note

Low Risk
Small auth redirect configuration change aligned with existing Electron behavior; no new routes or security logic.

Overview
Fixes T3 Connect web sign-up landing on a 404 after creating a new account (“Use a fresh account”). Sign-in already returned to the starting URL; sign-up did not.

resolveClerkSignInProps now sets signUpForceRedirectUrl to the same href as forceRedirectUrl on the non-Electron path, matching the Electron branch and what Clerk expects for post–sign-up redirects. Without it, Clerk used its dashboard default route, which this app does not serve.

The web unit test expectation is updated to assert both redirect props.

^{Reviewed by Cursor Bugbot for commit 1a56464. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Connect sign-up redirect to return to the app instead of a 404

When a user signs up via Clerk on the web (non-Electron) path, the redirect after sign-up was not set, causing a 404. resolveClerkSignInProps in authRedirect.ts now includes signUpForceRedirectUrl set to the same href as forceRedirectUrl for the non-Electron code path.

^{Macroscope summarized 1a56464.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1849e2d-4144-4c56-a9be-edfe06ef3769

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved c1d34e9

Straightforward bug fix adding the missing signUpForceRedirectUrl property to prevent 404s after sign-up. The pattern already exists in the Electron code path, and this change applies the same fix to the non-Electron path. Low risk with test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[juliusmarminge]

Closing as superseded by #5133, which is merged and includes the same signUpForceRedirectUrl: href behavior plus the corresponding authRedirect test coverage as part of the broader /connect authentication fix.