Fetch org gateway_api_url before launch#120
Merged
Merged
Conversation
The org's console-configured gateway_api_url is now authoritative when set; the local override (EDGEE_API_URL / profile gateway_url) applies only as a fallback. Also print the resolved gateway URL on launch claude.
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The CLI now routes coding agents through the gateway configured for the org in the console, instead of always using the built-in default.
At launch it resolves the gateway base URL with this precedence:
EDGEE_API_URLenv > profilegateway_url> org'sgateway_api_url(fetched fresh viaGET /v1/organizations/:id) > built-in default.The org fetch is best-effort — any failure falls through to the next source, so launch never breaks. Wired into all launch commands (claude/codex/crush/opencode).