anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Support OpenRouter OAuth PKCE authentication #4711

New Issue
Open
opened 2026-02-16 17:45:08 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:45:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @Void-n-Null on GitHub (Jan 11, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

Currently, OpenRouter authentication only supports manually entering an API key. OpenRouter provides an OAuth PKCE flow that allows users to authenticate with their OpenRouter account directly, which is more convenient and aligns with how other providers (Anthropic, GitHub Copilot, OpenAI/Codex) handle authentication.

Proposed Solution

Add an internal authentication plugin for OpenRouter that implements the OAuth PKCE flow, following the same pattern as the existing CodexAuthPlugin.

The flow:

  1. Start a local HTTP server to receive the OAuth callback
  2. Open browser to OpenRouter authorization URL with PKCE challenge
  3. User authorizes in browser
  4. Exchange authorization code for API key
  5. Store the API key

Reference: https://openrouter.ai/docs/guides/overview/auth/oauth

Additional Context

This falls under "Support for new providers" in the contributing guidelines. The implementation follows established patterns in the codebase and requires minimal changes to existing files.

Originally created by @Void-n-Null on GitHub (Jan 11, 2026). Originally assigned to: @thdxr on GitHub. ## Problem Currently, OpenRouter authentication only supports manually entering an API key. OpenRouter provides an OAuth PKCE flow that allows users to authenticate with their OpenRouter account directly, which is more convenient and aligns with how other providers (Anthropic, GitHub Copilot, OpenAI/Codex) handle authentication. ## Proposed Solution Add an internal authentication plugin for OpenRouter that implements the OAuth PKCE flow, following the same pattern as the existing `CodexAuthPlugin`. The flow: 1. Start a local HTTP server to receive the OAuth callback 2. Open browser to OpenRouter authorization URL with PKCE challenge 3. User authorizes in browser 4. Exchange authorization code for API key 5. Store the API key Reference: https://openrouter.ai/docs/guides/overview/auth/oauth ## Additional Context This falls under "Support for new providers" in the contributing guidelines. The implementation follows established patterns in the codebase and requires minimal changes to existing files.
yindo commented 2026-02-16 17:45:08 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 11, 2026):

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

  • #5668: [FEATURE]: OpenRouter OAuth support

Feel free to ignore if this addresses a different aspect of OpenRouter authentication.

@github-actions[bot] commented on GitHub (Jan 11, 2026): This issue might be a duplicate of existing issues. Please check: - #5668: [FEATURE]: OpenRouter OAuth support Feel free to ignore if this addresses a different aspect of OpenRouter authentication.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4711
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?