Fix provider OAuth with non-localhost callback urls

[colinmollenhour]

Description

I run OpenCode on a separate compute and access it through tailscale so when I run the provider connections like OpenAI, Z.AI, etc they typically load a localhost-based url at the end to pass the auth code back to opencode. I know to either copy this url and run it on my remote host with curl or modify it to use my tailscale hostname, but many users might not know to do this and it's clunky.

I propose that an environment variable like OPENCODE_REMOTE_URL_HOST=my-tail-name be supported so that remote callback urls can be constructed according to the environment.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• This is a feature request (proposing a new OPENCODE_REMOTE_URL_HOST environment variable), but it uses the Bug Report template. Feature requests must use the Feature Request template, with a title starting with [FEATURE]: and include the required verification checkbox and description fields.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]: Allow custom OAuth redirect URI configuration for MCP servers #7377: [FEATURE]: Allow custom OAuth redirect URI configuration for MCP servers — requests configurable OAuth callback URLs for remote/custom host scenarios
• WSL2/devcontainer: MCP OAuth callback unreachable from host browser (Sentry) #9081: WSL2/devcontainer: MCP OAuth callback unreachable from host browser — same root cause (OAuth callback going to localhost that isn't reachable from a remote/container environment)

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.