Accept the documented REARM_URL / REARM_API_ID / REARM_API_KEY env spellings - #36
Merged
Conversation
…PI_KEY env spellings The auth env binding was derived purely from flag names (uri / apikeyid / apikey), so only REARM_URI / REARM_APIKEYID / REARM_APIKEY worked -- while the operator-facing docs (orientation.md section 1.1 and the agentic workflow page) tell people to export REARM_URL / REARM_API_ID / REARM_API_KEY, which the CLI silently ignored and then failed with `unsupported protocol scheme ""`. Multiple agent sessions independently re-discovered this and fell back to explicit -u/-i/-k flags. Bind both spellings explicitly for the auth trio. Precedence, verified empirically against a live instance: flags still override env; when both spellings are set the flag-derived one (REARM_URI et al) wins; each spelling authenticates alone, including on agent subcommands. ReARM-Agentic-Session: cli-env-aliases-1785637582 ReARM-Agent: 62df357e-a3a4-4df5-82d4-049e629d1c6b Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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's env auth binding was derived purely from flag names (
uri/apikeyid/apikey), so onlyREARM_URI/REARM_APIKEYID/REARM_APIKEYworked — while the operator-facing docs (orientation.md §1.1 and the agentic workflow page on the documentation site) tell people to exportREARM_URL/REARM_API_ID/REARM_API_KEY. Those were silently unbound: the CLI fell through to empty values and failed withPost "/graphql": unsupported protocol scheme "". Multiple agent sessions independently re-discovered this and worked around it with explicit-u/-i/-kflags.Fix: explicit
BindEnvfor the auth trio accepting both spellings. Docs need no changes — they become correct.Precedence, each case verified empirically against a live instance:
REARM_URL/REARM_API_ID/REARM_API_KEYalone → authenticates (was broken);REARM_URI/REARM_APIKEYID/REARM_APIKEYalone → still authenticates (no regression);REARM_URIet al) wins;-uflag → still overrides env entirely;Blast radius: CLI-only, additive, all subcommands; no behavior change for anyone currently using flags or the flag-derived names.
🤖 Generated with Claude Code