Skip to content

feat: custom-openai provider namespace with separate env vars - #3338

Merged
Yeachan-Heo merged 1 commit into
mainfrom
lane/pr-3248
Oct 13, 2026
Merged

Yeachan-Heo merged 1 commit into
mainfrom
lane/pr-3248

Conversation

@Yeachan-Heo

Copy link
Copy Markdown
Contributor

This PR integrates the custom-openai provider namespace feature from PR #3248.

Changes

  • Add 'custom-openai' provider kind to setup_wizard with distinct CLAWCUSTOMOPENAI_* env namespace
  • Add CustomOpenAi variant to ProviderConfigKind enum
  • Implement OpenAiCompatConfig::custom_openai() for custom-openai endpoints
  • Update model resolution to handle 'custom-openai/' prefix
  • Add configuration persistence tests

Testing

  • Unit tests pass for custom-openai specific functionality
  • Setup wizard correctly prompts for custom-openai with separate env vars
  • Provider configuration survives runtime boundary

Supersedes #3248

Co-authored-by: TheArchitectit thearchitectit@users.noreply.github.com

- Add 'custom-openai' provider kind to setup_wizard.rs with distinct env namespace
- Add CustomOpenAi variant to ProviderConfigKind enum in api/client.rs
- Implement OpenAiCompatConfig::custom_openai() for custom-openai endpoint
- Update explicit_provider_kind_for_model() to handle 'custom-openai/' prefix
- Add tests for custom-openai configuration persistence across runtime boundary

Co-authored-by: TheArchitectit <thearchitectit@users.noreply.github.com>

Fixes #3248
@Yeachan-Heo
Yeachan-Heo merged commit 9428051 into main Oct 13, 2026
6 checks passed
@XinwangTao

Copy link
Copy Markdown

Separate env namespace for custom-openai endpoints is a clean way to avoid collisions with the built-in OpenAI vars — nice that the setup wizard guides through it too. Good consolidation of #3248.

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.

2 participants