Uh oh!
There was an error while loading. Please reload this page.
fix: resolve console device URLs - #44029
Merged
Merged
Conversation
kitlangton
enabled auto-merge (squash)
August 22, 2026 00:15
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Aug 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Port the Console device authorization URL fix to both implementations currently present on
dev.Before / After
Before: The Console API returns an origin-rooted
/console/device?...verification path. Both dev implementations appended that value to the path-bearinghttps://opencode.ai/consoleserver string, producing/console/console/deviceand routing signed-in users to their organization instead of device approval.After: Both implementations use standard URL resolution. Origin-rooted paths resolve from the origin, path-relative values resolve beneath the configured server base, absolute HTTP(S) URLs remain unchanged, and malformed or non-HTTP(S) values enter each implementation's existing typed error channel.
How
packages/opencode/src/account/account.tsresolves the verification URL insideAccount.loginand maps invalid values toAccountServiceError.packages/core/src/plugin/provider/opencode.tsresolves the verification URL inside the existing V2 OAuth method and maps invalid values throughIntegration.AuthorizationError.Scope
This does not change account APIs, integration APIs, endpoints, credentials, token polling, or the Console response. It only replaces string concatenation at the two verification URL boundaries on
dev.Testing
bun run test test/account/service.test.tsfrompackages/opencode: 15 passedbun run test test/plugin/provider-opencode.test.tsfrompackages/core: 12 passedbun typecheckfrompackages/opencodebun typecheckfrompackages/coregit diff --checkFlow
Ports the fix from #44021 to
dev.