OIDC support?

[PylotLight]

Any chance at adding support for public hosted instances behind oidc/openid auth?

[dzianisv]

Thanks for raising this. I’m scoping the smallest interoperable path rather than assuming every reverse-proxy OIDC setup behaves the same. Could you share:

1. Which IdP/proxy you use (for example Authentik, Authelia, oauth2-proxy, Cloudflare Access, or Tailscale)?
2. Does the hosted instance work through a normal browser redirect/login flow today, or does it expose bearer tokens/API credentials for non-browser clients?
3. Would an in-app browser login that persists the resulting session cookie cover your setup?

I’ll use the answers to define the compatibility target and an acceptance test before implementation.

[PylotLight]

I currently use https://voidauth.app/#/
Errm not checked how it exposes auth/tokens.
Potentially?

Apologies for being less than helpful

[dzianisv]

Triaged. Valid feature request, deferred with rationale: OIDC/OpenID auth for hosted opencode instances fits the OpenCode Connect roadmap (managed/hosted access), not the current self-hosted direct-connect path. The app today does Basic auth to a user's own server; OIDC needs an auth-code/token flow + token storage + refresh, which is scoped work that belongs with the hosted-instance (Connect) effort. Keeping open as a tracked enhancement, tagged to the Connect roadmap. Not a quick fix; will schedule with Connect build.