v0.14.0 — Optional Muse Code and OpenCode 2

Setup → Agents now offers optional Muse Code installation and OpenCode 2 in the existing OpenCode version picker.

• Muse Code: install only when requested, sign in with a Meta device code or save an API key, and keep credentials on the persistent volume. T3 Code checks Muse sign-in on the first message; saved credentials alone are not reported as verified.
• OpenCode 2: choose Install a specific version… on the OpenCode row and search for 2. The official @opencode/cli package is installed through mise. Updates stay within the selected major, and a failed switch preserves the previous selection.
• Defaults: the image starts with T3 Code Stable and OpenCode 1; Muse is excluded from the default first-start installs. Using Muse or OpenCode 2 in T3 Code requires Nightly, selectable under Setup → Environment.

OpenCode 2 requires version 2.0.18 or newer. Before switching majors, stop running OpenCode sessions and back up its data. OpenCode 2 converts the shared database on first use; installing an older CLI does not restore that database. The setup panel explains this before starting the switch.

Update the container image to v0.14.0 to get the new setup panel and installer support. T3 Code itself continues to support in-container Stable/Nightly switching.

Images for Linux amd64 and arm64:

• Browser: ghcr.io/dizys/t3code-docker:0.14.0 or :0.14.0-browser
• Core: ghcr.io/dizys/t3code-docker:0.14.0-core
• The latest, browser, full, core, and slim tags point to this release.

All 387 Node tests pass, including Muse CLI dispatch regressions. Release CI passed both image variants on both architectures, including native smoke tests and the amd64 agent lifecycle tests. Published manifests and image version/source labels match the tested release digests. Real ARM64 CLI lifecycle and desktop/mobile setup panel flows were also verified locally.

Implementation and validation · Release validation · Full changelog

v0.13.2 — Reliable Nightly channel switches

Switching T3 Code from Stable to Nightly now gives the first database import enough time to finish. Large thread histories could previously hit a 30-second limit and show a misleading paired-device compatibility error.

• Allow two minutes for database preparation and native device-access validation.
• Distinguish preparation timeouts from incompatible pairing records.
• Preserve database backups, authentication checks and automatic rollback.

Update the container image to v0.13.2 to get this supervisor fix. Afterward, T3 Code channel switches and updates continue to run inside the container.

Images for Linux amd64 and arm64:

• Browser: ghcr.io/dizys/t3code-docker:0.13.2 or :0.13.2-browser
• Core: ghcr.io/dizys/t3code-docker:0.13.2-core
• The latest, browser, full, core, and slim tags point to this release.

All 367 Node tests pass, including slow-import and rollback regressions. Release CI passed both image variants on both architectures, including native smoke tests and the amd64 agent lifecycle tests. Published manifests match the tested image digests.

Fix and validation · Release validation · Full changelog

v0.13.1 — T3 Code update card polish

The T3 Code update card in Setup → Environment now matches the console's shared controls and spacing.

• Use the standard compact Stable/Nightly selector on desktop, with 44 px touch targets on phones.
• Show update status and versions in a clean row without the shaded inset or stray border.
• Give footer buttons proper spacing below the divider.
• Keep long Nightly version strings and their upgrade arrow together, with the status icon aligned to its label.

Update your container image to v0.13.1 to get these Setup improvements.

Images for Linux amd64 and arm64:

• Browser: ghcr.io/dizys/t3code-docker:0.13.1 or :0.13.1-browser
• Core: ghcr.io/dizys/t3code-docker:0.13.1-core
• The latest, browser, full, core, and slim tags point to this release.

All 64 responsive browser checks and seven Setup rendering tests pass. Release CI passed for both image variants on both architectures, including native smoke tests and the amd64 agent lifecycle tests. Published manifests match the tested image digests.

Changes and before-and-after screenshots · Release validation · Full changelog

v0.13.0 — T3 Code update channels

T3 Code can now be upgraded directly from Setup → Environment without replacing or restarting the container. Choose Stable or Nightly, check the latest published release, and confirm when to install. Switch back to Stable whenever you prefer. Updates within a channel never downgrade a newer installed version.

Only the T3 Code process restarts; Setup and the container stay running. Active agent turns and T3 terminals stop during activation, and open clients reconnect. The installed version and release channel persist on the home volume across restarts and image upgrades.

Downloads use the official architecture-specific package, verify its SHA-512 integrity, and check launcher compatibility before stopping the current server. SQLite snapshots and the native prepared/commit handshake protect activation: a failed, timed-out, or interrupted trial restores the previous version and database. Progress, errors, and retry controls are shown in Setup.

Upgrade your container image once to v0.13.0 to enable this feature. Later T3 Code updates can happen inside the container. Setup, OS dependencies, and future supervisor requirements still update through images. The bundled Stable release remains T3 Code 0.0.45.

Current Stable and Nightly use different thread databases. Both histories are kept, but returning to Stable can show earlier history. Some devices may need pairing again when the releases use different signed credential permissions. Pairing records and revocations transfer across compatible schemas; a switch is refused if it would broaden a restricted credential's permissions. The confirmation explains these consequences before installation.

Images for Linux amd64 and arm64:

• Browser: ghcr.io/dizys/t3code-docker:0.13.0 or :0.13.0-browser
• Core: ghcr.io/dizys/t3code-docker:0.13.0-core
• The latest, browser, full, core, and slim tags point to this release.

All 364 Node tests pass. Each platform image passed its smoke tests; both amd64 variants passed the real agent lifecycle tests before publication. Release manifests were verified against the tested image digests. A real Stable → Nightly → Stable round trip and eight responsive browser contexts were also verified; screenshots and the recording are in the PR.

Changes and UI demos: #21

Validation: https://github.com/dizys/t3code-docker/actions/runs/38174465889

Full changelog: v0.12.0...v0.13.0

v0.12.0 — Rename paired devices

Paired devices can now be renamed from Setup without unpairing them or changing their credentials or session expiry. Labels persist across container recreations; clearing a label restores the original device name.

The rename form uses a compact, centred dialog on desktop and a short bottom sheet on phones. It includes device context, a live character counter, keyboard controls, comfortable touch targets, and inline errors that preserve your input. Save is enabled only when the label changes, and pending saves cannot be submitted twice.

Includes T3 Code 0.0.45 and the reliable agent updates introduced in v0.11.1.

Images for Linux amd64 and arm64:

• Browser: ghcr.io/dizys/t3code-docker:0.12.0 or :0.12.0-browser
• Core: ghcr.io/dizys/t3code-docker:0.12.0-core
• The latest, browser, full, core, and slim tags point to this release.

Each platform image passed its smoke tests; both amd64 variants passed the real agent lifecycle tests before publication. Release manifests were verified against those tested image digests.

Changes and UI demos: #20

Validation: https://github.com/dizys/t3code-docker/actions/runs/37889049792

Full changelog: v0.11.1...v0.12.0

v0.11.1 — Reliable agent updates

Agent updates now install the newest published stable release immediately, bypassing mise's release-age delay and refreshing its remote-version cache. If you already have a newer version installed, Update keeps it and explains why. Repeated updates of a healthy current install report that it is already up to date.

This also protects agents that updated themselves in place, verifies the executable's version before accepting an install, and rolls back selection on a mismatch. Toolchain, source-control, and added-tool updates retain newer installed versions too. Deliberately selecting a specific older version remains supported.

Includes T3 Code 0.0.45, the current stable release at publication.

Images for Linux amd64 and arm64:

• Browser: ghcr.io/dizys/t3code-docker:0.11.1 or :0.11.1-browser
• Core: ghcr.io/dizys/t3code-docker:0.11.1-core
• The latest, browser, full, core, and slim tags point to this release.

Each platform image passed its smoke tests; both amd64 variants passed the real agent lifecycle tests before publication. Release manifests were verified against those tested image digests.

Changes: #19

Validation: https://github.com/dizys/t3code-docker/actions/runs/37852507562

Full changelog: v0.11.0...v0.11.1