[Feature]: Add Command Code as a built-in provider

[AbdurehmanSaleemi]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/desktop

Problem or use case

There's no way to use Command Code (command-code CLI) as a provider inside T3 Code. Users who prefer Command Code as their coding agent have to run it separately instead of managing it alongside Claude, Codex, Cursor, Grok, and OpenCode from within T3 Code.

Proposed solution

Add a Command Code provider driver that auto-discovers the command-code CLI, probes its auth status and available models, and exposes it as a first-class provider in T3 Code's provider settings. Includes a text generation adapter for commit messages, PR content, branch names, and thread titles, plus the same auto-provisioning pattern used by other default providers.

Why this matters

Users who already run Command Code can manage it from the same UI as their other providers. T3 Code gains parity with the provider ecosystem Command Code belongs to (Claude Code, Codex, Cursor, etc.) without requiring users to context-switch.

Smallest useful scope

A first pass only needs to auto-provision the Command Code provider, successfully probe its status (installed + authenticated), and show it in the Providers settings.

Alternatives considered

I didn't add it to the legacy settings.providers schema (as the plan doc says), and I opted for auto-discovery rather than requiring manual config.

Risks or tradeoffs

The command-code CLI is an npm package, not bundled with T3 Code, so the provider only shows as "installed" when the user has it on PATH. Windows .cmd shim resolution needs careful shell handling.

Examples or references

Contribution

• I would be open to helping implement this.

[Malix-Labs]

Blocked by : CommandCodeAI/command-code#331

[Splaxi]

I have a working alpha version of a "bridge" between T3 and commandcode cli. It acts as the ACP endpoint. It works via pnpm dev, which starts a web backend, that I can connect to. It resembles the real T3 app. It uses the headless option from commandcode, and seems to work - while we wait for the full ACP support directly in commandcode.

Not sure if @t3dotgg and the team would be willing to work with my crude implementation, to see if we can get it up and running 🤞