Skip to content

v0.3.0: orchestrator V2 only

Latest
Latest

Choose a tag to compare

View all tags
@MajesteitBart MajesteitBart released this 04 Oct 08:24
· 2 commits to main since this release
v0.3.0
a92548e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.3.0 ports the CLI to T3 Code's orchestrator V2.

It works only with T3 Code builds that include orchestrator V2. It checks the server's protocol before it signs in. On a T3 build without orchestrator V2, every command that talks to T3 except doctor stops with T3_PROTOCOL_UNSUPPORTED (exit code 4), and the message points to 0.2. doctor reports checks.orchestrationProtocol.ok: false instead and exits with 1. There is no fallback to orchestrator V1.

Which version you need

T3 Code build Orchestrator CLI Install
Nightly 0.0.46-nightly.20261003.2610 or later V2, protocol 2 0.3 npm install --global @bvdm/t3code-cli
Stable v0.0.45 or earlier, or an earlier nightly V1, protocol 1 0.2 npm install --global @bvdm/t3code-cli@0.2

At the time of this release, no stable T3 Code release includes orchestrator V2. If you run stable T3 Code, stay on 0.2, because a plain npm install --global @bvdm/t3code-cli now installs 0.3. t3code --json doctor shows what your server speaks under checks.orchestrationProtocol.

What changed

  • Sign-in. The CLI runs the t3 command that matches the server's version: a configured command, the running server's own executable on Linux, the installed desktop app's t3, a matching t3 on PATH, or npx t3@<server version>. The bundled t3 package is gone.
  • Handovers. One orchestration.launchThread call creates the thread, prepares its workspace or new worktree, and starts the prompt. handover --wait returns the first reply. A handover into the project checkout or an existing worktree records that checkout's branch on the thread, as T3's own app does.
  • Threads as runs. Reads, waits, and busy checks use T3's runs and runtime requests. A fork's inherited history shows as inherited turns. Turns from before orchestrator V2 show as imported, because T3's migration kept only their messages.
  • Sending. --if-busy refuse (default), queue, steer, or restart.
  • Settings. threads set --provider switches a thread to another provider through T3's handoff.
  • New commands. threads fork, merge-back, queue list|edit|cancel|move|promote|resume, search, pin, unpin, snooze, unsnooze, archive, unarchive, rename, and schedules list|create|update|enable|disable|delete|run.
  • Verification. Every write is checked in T3's state before the CLI reports success.
  • Fix. Server discovery no longer crashes Node 26 on Windows at exit.

Scripts that read the JSON output should check Upgrading from 0.2 in the README for the breaking changes.

Since beta.2

  • Handovers record the checkout's branch, as described above. Before, a thread started from inside a worktree had no branch, so T3 could not use it to find pull requests or settle the thread.
  • The README, the npm description, --help, and both shipped skills now state the orchestrator V2 requirement.
  • The README documents two Windows shell caveats. Windows PowerShell 5.1 drops double quotes from prompt arguments and sends stdin as ASCII. Git Bash rewrites a prompt that starts with / into a Windows path.

Both betas went through full user tests against V2 nightlies, on Linux with beta.1 and on Windows 11 with beta.2.

Assets 2
Loading