ACP harness · MIT · verified on command‑code v1.89.1

Command Code inside T3 Code,
in one script.

The commandcode CLI already speaks the Agent Client Protocol. T3 Code already speaks it too. This repo connects the two, so your Command Code subscription shows up as a normal provider next to Claude, Codex and Cursor — no proxy, no wrapper, no API key.

shell
$ git clone https://github.com/jovylle/t3-command-code-harness.git
$ cd t3-command-code-harness
$ ./install.sh

==> commandcode: /Users/you/.local/bin/commandcode
==> backup: ~/.t3/userdata/settings.json.bak.2026-11-16T10-25-41-000Z
==> added providerInstances.acpRegistry_command_code
==> ready - 98 models
==> first: deepseek/deepseek-v4.1-flash, ...

Done. In T3 Code open the model picker and choose Command Code.
  • 0 API keys
  • 98 models at last probe
  • 1 file touched
  • MIT licensed

How the pieces connect

app T3 Code
process commandcode acp
account your subscription

Nothing runs in the background. No port is forwarded. T3 spawns the CLI, sends initialize and session/new, and every turn after that is plain ACP traffic.

What you get

A provider, not a workaround

Command Code is exposed the same way every other T3 provider is — which means threads, model switching, permission modes and usage tracking all behave normally.

Provider in the model picker

Command Code appears as a provider. Pick a model per thread like any other harness.

Your own model catalog

The list comes from Command Code, not this repo — roughly 98 models today, default deepseek/deepseek-v4.1-flash.

Existing login, reused

It reads ~/.commandcode/auth.json. If you are signed in to the CLI, T3 just works — no re-auth, no token copy-paste.

Permission modes map through

T3's mode switches land on Command Code's own modes: Standard, Accept Edits, Plan, Don't Ask, Bypass.

Install

Three commands, one JSON key

The script is idempotent: run it twice and it tells you there is nothing to change. Your settings file is backed up before every write.

  1. Check the prerequisites

    T3 Code (with the acpRegistry provider driver), the CLI, and a Node runtime — T3 ships one.

    $ commandcode --version
    $ commandcode login          # only if you are not signed in
    $ ls ~/.commandcode/auth.json
  2. Run the installer

    It finds the binary (or honors COMMANDCODE_BIN), edits ~/.t3/userdata/settings.json, and waits for T3 to hot-reload the provider.

    $ git clone https://github.com/jovylle/t3-command-code-harness.git
    $ cd t3-command-code-harness
    $ ./install.sh
  3. Pick the provider

    Open T3, hit the model picker, choose Command Code. Restart T3 only if the provider does not appear.

Manual install — the exact JSON

Add this under providerInstances in ~/.t3/userdata/settings.json, with your own command -v commandcode path:

{
  "providerInstances": {
    "acpRegistry_command_code": {
      "driver": "acpRegistry",
      "displayName": "Command Code",
      "enabled": true,
      "config": {
        "source": "local",
        "commandPath": "/Users/you/.local/bin/commandcode",
        "commandArgs": ["acp"]
      }
    }
  }
}
Uninstall

Removes the provider entry (backing up settings first) and deletes the probe cache. Restart T3 if it is still listed.

$ ./uninstall.sh

Gotchas

Four things that will bite you

Learned the hard way, written down so you do not repeat it.

01

Don't-ask mode silently kills tools

In a non-prompting permission mode, any tool outside the allowlist is denied with no prompt. It looks like the agent is broken when it is really the harness refusing. Use Accept Edits or Plan, or add explicit permissions.allow rules.

02

The CLI self-updates mid-thread

If the CLI updates while a session is live, that session can break. Finish or reopen the thread instead of expecting the old one to keep going.

03

The model list is not in this repo

T3 asks the CLI. Different Command Code plans expose different models, so two people can see different pickers on the same commit.

04

Version drift is real

Verified against v1.89.1. If acp disappears from commandcode --help, the flag was renamed — the fix is one string in settings.json.

You already pay for Command Code.
Now use it in T3.

One script, one settings key, your existing login.