Skip to content

fix(web): unstick /connect after in-modal sign-in by redirecting to the authorize endpoint - #5133

Merged
juliusmarminge merged 1 commit into
pingdotgg:mainfrom
TorbenWetter:fix/connect-passkey-fragment-redirect
Aug 15, 2026
Merged

fix(web): unstick /connect after in-modal sign-in by redirecting to the authorize endpoint#5133
juliusmarminge merged 1 commit into
pingdotgg:mainfrom
TorbenWetter:fix/connect-passkey-fragment-redirect

fix(web): unstick /connect after in-modal sign-in by redirecting to t…

7a839fb
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - UI Consistency succeeded Aug 15, 2026 in 18s

All clear

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/ui-consistency.md
More information about how Check Run Agents work can be found in our Help Center.


🔍 Agent activity — reasoning, no tool calls

💭 Looking at the changed files to see what needs evaluation. I notice the diff is mostly logic changes rather than UI styling, and I'm spotting a potential hook issue in ConnectCliAuthSurface.tsx where isElectron is used inside the openSignIn callback but might be missing from the dependency array. Let me check whether isElectron is a constant or a value that could change. I'm checking whether the Button primitive is being used consistently and whether changing signUpForceRedirectUrl impacts other places that call resolveClerkSignInProps. This doesn't seem to be a UI styling concern, though I should verify that connectCliAuth.ts isn't affected by the changes. The scope here is UI consistency, and there are no styling changes in the diff, so I think we're good. I need to format my response as JSON with a success state and "All clear" as both the title and summary, then do a final sanity check on the fallback test behavior when the environment variable isn't set.


Agent Credits: 21 credits