Known limits

A few things work differently here — and why.

None of the below is a bug we're hiding. Each one falls out of something GateGlass does on purpose: a throwaway browser profile, and driving a real browser from the outside. Where there's a workaround, it's the first thing listed.

Passkeys need a separate device Sign-in

You see: Windows says "Something went wrong — There was a problem signing in with your passkey."
Why: GateGlass starts a fresh browser profile every session, which is the whole point of it. Passkeys saved to Google Password Manager, or stored inside another browser profile, simply aren't in that profile to use. Windows never receives a credential it recognises, so it shows its own generic error.

Do this: Choose "Use a phone or tablet" and scan the QR code, or use a hardware security key. Both work normally. A passkey saved to Windows Hello on this PC also works, because Windows stores that one, not the browser.

Installing an extension or GX mod takes two clicks Extensions

You see: You click Install, approve GateGlass's prompt — and the store page just sits there.
Why: The package has to be handed to the browser's own installer, and only a real click does that. If GateGlass re-issued the click for you, the browser would treat the package as a file download instead and drop an inert .crx in your Downloads folder — which is exactly what used to happen.

Do this: After approving the prompt, click Install again on the store page. The browser installs it from there. The approval stays open for a minute, so there's no rush.

Opera GX's own settings pages come up blank Opera GX

You see: With GX carryover, GX's built-in pages — Mods, GX Control, Shaders, GX Cleaner — render empty.
Why: Nothing is being blocked. We checked: the pages load completely, their scripts run, and the audit log records zero denials. Chromium simply stops painting a surface it considers hidden, and these are the browser's own internal pages rather than web pages. The content is all there — it just never draws.

Do this: Set your mods and GX settings up in normal Opera GX first, then launch through GateGlass with carryover. Carryover runs your real profile in place, so everything you configured comes with you.

Why we'd rather list these than quietly paper over them. Two of the three are the direct cost of features you're paying for. The throwaway profile is what makes a session disposable — and it's the same reason a saved passkey isn't sitting in it. Driving a real browser from outside is what lets you see and stop requests before they leave your machine — and it's the same reason the browser's own internal pages behave oddly. Hit something that isn't listed here? Tell us — the fixes usually land for everyone at once.