Skip to content

Omarchy T3 Code v0.2.19

Choose a tag to compare

@avillagran avillagran released this 22 Oct 04:47
· 130 commits to d1719c8efc4aba9d7e5e8049d948db4ea003a67d since this release

Native aarch64 and x86_64 packages for Omarchy on Arch Linux. Install or update with the README one-liner:

curl -fsSL https://raw.githubusercontent.com/avillagran/omarchy-t3-code/main/install.sh | bash

Highlights

A desktop app beside the bar

ot3 no longer runs inside the Omarchy shell. It is its own Quickshell process, started as a user service:

  • A stuck bar no longer blocks ot3, and restarting the shell keeps your chats open. Super+Shift+A goes straight to the app.
  • Smoother: the app holds 120 fps on its own process instead of sharing the shell's.
  • Panel mode is kept. With the bar widget, the header's window button still cycles panel → floating → tiled; the panel opens under the bar's T3 button on the monitor you used, as before.
  • Floating windows have resize corners and edges, and open at their saved size, centred.
  • The installer adds an Omarchy T3 Code entry to the app launcher, a hidden start at login and ot3 on your PATH (ot3, ot3 hide, ot3 quit, ot3 restart, ot3 status). The bar widget stays optional (OT3_BAR_WIDGET=0) and only shows the work/ready/input badges.

Connections that do not stall

  • A remote that does not answer no longer slows the others: sending, pasting images and switching OmaBridge routes answer at once while it retries, with a growing wait between attempts.
  • SSH environments connect to the server T3 Desktop already launched when its server-runtime.json is missing, instead of reporting t3_remote_start_failed.
  • The sidebar's machine button lists every environment with its state and T3 version, a Reconnect, and a confirmed Restart server that kills T3 on that host and starts it again.

Composer

  • Follow-up behavior as in T3: messages sent during a run are queued or steer the run, following T3's own setting (shared with T3). Hold Ctrl over the send button, Ctrl-click or Ctrl+Enter for the other one.
  • Attachments show as chips in the text with name and size, and images as thumbnails above it.
  • Permissions are an icon; tasks, queue, approvals, questions and the live status line keep the composer's width.

Also new

  • Provider updates: a notice when Claude, Codex or another harness has a new version, and Update all across every environment, one after another.
  • Thread details: open in your editor, project scripts, version control and lineage, resizable.
  • Why a run failed: the failed tools with their input and output, in the error card and the timeline.
  • Inline paths look like links, without separate chips.
  • T3 Code compatibility in Preferences → General: the T3 version ot3 is validated with and each server's version; newer servers are marked.

For developers

  • One pinned T3 Code revision (upstream/t3code.json) for every generator.
  • tools/upstream-drift.cjs reports what a newer T3 nightly adds or removes (RPC methods, orchestration events, HTTP endpoints, settings, keybindings) and what ot3 does not cover, with a parity inventory in upstream/parity.json. tools/upstream-watch runs it against the newest nightly tag.

Checksums (SHA-256)

891853aae65b2b759778c27028651567f2a27aaf626927069dad6c58c859cf96  omarchy-t3-code-v0.2.19-linux-aarch64.tar.gz
8f7a6e2634b7a75b7e46246b138b9914128b72afbd0e5d31c6e4522b6505cf6e  omarchy-t3-code-v0.2.19-linux-x86_64.tar.gz