Skip to content

feat/provider command names - #75

Merged
shettydev merged 5 commits into
mainfrom
feat/provider-command-names
Sep 22, 2026
Merged

shettydev merged 5 commits into
mainfrom
feat/provider-command-names

Conversation

@shettydev

Copy link
Copy Markdown
Owner
  • test(cli): Cover naming a provider by the command it runs
  • feat(cli,scripts): Name each provider after the command it runs
  • test(api): Cover the launcher's provider names as AI_PROVIDER values
  • feat(api): Accept the launcher's provider names in AI_PROVIDER
  • docs(cli,config): Document the provider names as claude and agy

Description

Changes

Testing

Screenshots (if applicable)

Checklist

  • Code follows project style guidelines
  • Tests added/updated
  • Documentation updated (if needed)
  • No breaking changes (or documented if any)

Additional Notes

`--provider claude-code` is a name only this project uses; the CLI people
already have installed is `claude`. These tests state the naming the launcher
should have — the id is the command — and keep the former names resolving from
the flag, `AI_PROVIDER` and a saved default, so nobody's config has to be
rewritten.
The id is what `--provider` takes, what is saved as the default and what is
passed on as `AI_PROVIDER`, so it should be the name the user already knows the
CLI by: `claude` and `agy`, not `claude-code` and `antigravity`. The former
names move to a per-provider `aliases` list and are still accepted everywhere a
provider can be named, so saved defaults and older scripts keep working.
The launcher passes the provider it chose straight through as `AI_PROVIDER`,
and it now names them after their commands, so `claude` and `agy` have to reach
the same adapters as `claude-code` and `antigravity` or local mode stops
booting.
`claude` and `agy` resolve to the adapters registered as `claude-code` and
`antigravity`, so the name the launcher hands over is the name the API
understands. Aliasing rather than renaming the adapters leaves every existing
`.env` working, and the no-key message now names the CLIs the way users meet
them.
The quickstart, the local-mode guide and the env example all taught the old
names; they now teach the command names, and say once that the former ones are
still accepted rather than repeating it at every mention.
@shettydev shettydev self-assigned this Sep 22, 2026
@shettydev
shettydev merged commit 5b1b78f into main Sep 22, 2026
2 checks passed
@shettydev
shettydev deleted the feat/provider-command-names branch September 22, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant