Add support to BYOK to command code here

[RK-625]

Feature Description

This improve and provide the users to have there api keys to be utilised here if the credits expire

Use Case

No response

Additional Context

No response

How important is this to you?

None

[pizofreude]

Proposal: Extend BYOK Support to Azure OpenAI and Xiaomi MiMo

To maximize flexibility for users whose credits expire or who require strict data sovereignty, I propose extending Bring Your Own Key (BYOK) support to Azure OpenAI and Xiaomi MiMo.

Currently, enterprise users are locked into platform credits. Allowing them to inject their own API keys for these specific providers would enable uninterrupted workflows using the preferred harness (CommandCode over the others) and better cost management.

1. Xiaomi MiMo API Integration

MiMo offers an OpenAI-compatible endpoint. BYOK support should allow users to route requests through their own keys using the standard OpenAI schema.

Documentation: Xiaomi MiMo API Docs

Implementation Note: The provider should map standard chat completions to MiMo's endpoint, accepting a user-provided X-MiMo-Api-Key or generic Authorization header.

2. Azure OpenAI BYOK

Azure requires specific handling for the api-version and instance-specific URLs. Users need the ability to input their AZURE_API_KEY, AZURE_ENDPOINT, and AZURE_DEPLOYMENT_NAME.

Working API Example: The following curl command demonstrates the current working pattern for Azure on Opencode (using the 2025-04-01-preview version and gpt-5.3-codex model):

curl -X POST "https://<instance-name>.openai.azure.com/openai/responses?api-version=2025-04-01-preview" \
  -H "Content-Type: application/json" \
  -H "api-key: $AZURE_API_KEY" \
  -d '{
    "model": "gpt-5.3-codex",
    "input": "hello",
    "max_output_tokens": 512
  }'

Technical Implementation Steps

Environment Variables: Add support for:

• XIAOMI_MIMO_API_KEY
• AZURE_API_KEY
• AZURE_INSTANCE_NAME
• AZURE_API_VERSION (default to 2025-04-01-preview)
• Provider Routing: Update the model selector to detect these keys. If present, route the request to the respective BYOK endpoint instead of the default credit-based gateway.
• Fallback Logic: If the user's BYOK key fails (e.g., rate limited or invalid), gracefully fallback to platform credits if available, or return a clear error.

This change would significantly improve the utility of the tool for enterprise users and developers managing multi-provider costs.

[ahmadawais]

We want to enable BYOK.

The only problem is we need to disengage all of our services for BYOK users so it doesn't put pressure on our systems when not needed.

That work is pending. And priority of fixing bugs is more than this.

But it's definitely coming.