ACP does not expose BYOK providers/models from providers.json #993

Summary

Command Code correctly loads BYOK providers from ~/.commandcode/providers.json in the CLI, but those providers and models are not exposed through ACP.

This means ACP clients such as T3 Code only see the built-in Command Code model catalog and cannot use models configured through BYOK.

The same BYOK models are available through cmd --list-models and work in the regular Command Code CLI.

Expected Behavior

If a BYOK provider is loaded by Command Code and appears in cmd --list-models, then the same provider/model IDs should also be exposed through ACP.

For example, if Command Code reports:

CLIProxyAPI (local) (byok)
cliproxy/gpt-6-astra GPT-6 Astra
cliproxy/gpt-6.1-sol GPT-6.1 Sol
cliproxy/gpt-6-sol GPT-6 Sol
cliproxy/gpt-6-luna GPT-6 Luna

then an ACP client should receive and be able to select those same model IDs.

ACP model discovery should use the same effective model registry as cmd --list-models and /model.

Actual Behavior

The CLI sees the BYOK provider correctly:

cmd --list-models | grep -i cliproxy

Output:

CLIProxyAPI (lokalne) (byok)
cliproxy/gpt-6-astra GPT-6 Astra
cliproxy/gpt-6.1-sol GPT-6.1 Sol
cliproxy/gpt-6-sol GPT-6 Sol
cliproxy/gpt-6-luna GPT-6 Luna

However, when running Command Code through cmd acp, an ACP client such as T3 Code only receives the built-in Command Code model catalog.

The BYOK models are missing.

T3 Code supports manually adding custom model IDs for ACP providers, so I also tried adding cliproxy/gpt-6-astra manually.

The model then appears in the T3 Code model picker, but starting a session fails with:

Failed to open acpRegistry provider session

This suggests the issue is not only model discovery. The ACP session path also does not appear to accept or route the BYOK model ID.

Steps to reproduce the issue

1. Add a BYOK provider to ~/.commandcode/providers.json.
2. Run cmd --list-models and confirm the provider/model appears.
3. Start Command Code with cmd acp.
4. Connect from an ACP client such as T3 Code.
5. Check the available models.
6. Observe that built-in Command Code models are available, but BYOK models are missing.
7. Manually add cliproxy/gpt-6-astra in the ACP client.
8. Start a session with that model.
9. Observe that the ACP provider session fails to open.

Command Code Version

1.75.1

Operating System

macOS

Terminal/IDE

t3-code

Shell

zsh

Session file (optional)

No response

Fix prompt (optional)

Make ACP use the same effective model registry as cmd --list-models and /model.

BYOK providers from ~/.commandcode/providers.json should be included in ACP model discovery, preserving their full model IDs such as cliproxy/gpt-6-astra.

ACP session creation and model switching should also accept those IDs and route them to the correct BYOK provider.

Verify with:

• a BYOK provider loaded from providers.json
• cmd --list-models
• cmd acp
• an external ACP client such as T3 Code
• selecting and successfully running a BYOK model through ACP

Additional context

This appears related to #954 : "Desktop app model picker never lists BYOK providers from providers.json (CLI does)".

That issue describes a similar mismatch where the CLI model registry includes BYOK providers but another Command Code frontend only sees the static catalog.

In this case the mismatch is between the normal Command Code CLI and the ACP interface.