Omarchy T3 Code v0.2.22

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

ot3 follows your Omarchy theme live

Switching themes with omarchy-theme-set (or the Omarchy menu) now recolors an open ot3 window at once, with no restart: the sidebar, conversation, composer, popups and the animated sky all follow the new theme.

Unified, themed tooltips

ot3's tooltips use Omarchy's unified tooltip style: the theme's colors, border and corner radius, centered above what they describe. They honor ~/.config/omarchy/tooltips.json (square, rounded or theme shape; theme, transparent or custom border), and a change there applies live.

Light themes look right

• Sidebar header: on light themes the header sky is a soft shade of the theme instead of a dark grey band, so the T3 Code logo and buttons read clearly.
• Stars and shooting stars are drawn in the theme's dark ink on light themes, so they show against a light sky. Dark themes are unchanged.

Also new since v0.2.20

v0.2.21 was tagged but never published, so its changes ship for the first time in this release.

Memory/Obsidian: one development vault on every computer

T3 keeps threads and decisions per environment and shares none of them between machines. Preferences → Memory/Obsidian sets up a shared development vault (a git repository of Obsidian notes) on the computer ot3 runs on, and keeps it in sync. See docs/JOURNAL_VAULT.md.

• Copy setup from comes first when a host already uses a vault, saying when your existing clone is reused; manual options wait under Other options.
• Finds the vault on your hosts. Each connected environment is read (never written) for a vault set up there, by ot3 or by hand in its agent instructions. Clones of the same remote count as one vault; with several you choose. An offline host shows as unknown, not as having no vault.
• Set up on this computer clones the same remote here, even when the selected environment runs its agents on another host. It uses this computer's own sign-in (it explains gh auth login or an SSH key when one is missing) and never copies credentials. A bare repository on a host is reached over its SSH profile or OmaBridge.
• Safe with existing folders. A clone of the same remote is reused, with Repair; a folder with other files or another remote is never overwritten.
• Agents on this computer get a marked block in ~/.claude/CLAUDE.md and ~/.codex/AGENTS.md; the rest of those files is kept, and running the wizard again changes nothing.
• Stays in sync: pull when ot3 opens and when a thread starts, commit journal(<project>) and push when threads settle. A conflict stops the sync and keeps local commits. New T3 projects get their Projects/<slug>/MEMORY.md, and this computer is listed in Machines.md.
• Commit identity: when the vault clone has no git name and email (common without a global identity), the one your checkouts here use is suggested, or set on its own when it already wrote the vault; only the vault's own config changes.
• Thread registry: when a thread settles, Projects/<project>/Threads.md gets its row (machine, title, t3-thread:// link, state): the 25 most recent titled threads of each project across every machine. Rows from several computers merge on their own.
• Agents search instead of loading: the agent protocol asks for rg over the vault and Threads.md before reading notes; an outdated block on this computer is renewed. Update 's agents installs it on an SSH host after confirming, writing only if the file did not change meanwhile.
• Search the vault from the command palette: notes under Memory (Obsidian); a hit that links a thread opens it, others open in Obsidian. Also omarchy-t3-client vault-search.
• Open in Obsidian, or how to install it when it is missing. The page says ready only when no step is pending.
• Without hosts: clone a remote by URL, or create a vault with a private GitHub repository.
• CLI: omarchy-t3-client vault-status, vault-discover, vault-sync [--push].

Dictation in the composer, in any language, on this computer

Speak your prompt instead of typing it, in Spanish, English, Portuguese, French, German, Italian or any of the ~100 languages Whisper knows, and switch between them from one dictation to the next. Speech becomes text locally with whisper.cpp; no audio leaves the computer and nothing keeps running in the background. See docs/DICTATION.md.

• Multi-language: the language is detected for each dictation, so a prompt in Spanish and the next one in English both come out right. Preferences → General → Dictation can fix one instead, which helps very short phrases.
• Microphone button next to Attach, or Ctrl+Space in the composer: hold to talk, or tap to start and tap again. Esc cancels. The text goes in at the cursor and Undo removes it.
• A live wave bubble rises out of the microphone as you speak: the last two seconds of sound against the room's noise, a pulsing dot and a recording timer. It is flat when nothing is heard, so you know the microphone is listening before you say a word.
• A muted microphone says so: the bubble shows Microphone muted · click to turn it on, and the click unmutes it.
• Nothing lost across pauses: pauses are shortened before transcription and the silence threshold follows your own voice, so a quiet microphone or a noise gate that cuts pauses to zero never drops what you said before them.
• Light: a 1.5 MB helper that lives only while you dictate. The model loads while you speak, so a 10-second prompt is ready about a second after you stop (Accurate model, M2 Pro).
• Two multilingual models, downloaded on first use and checked by SHA-256: Fast (82 MB) and Accurate (264 MB, default). Preferences → General → Dictation downloads and removes them.
• Names spelled right: the project, branch and thread title, plus your own vocabulary, guide the transcription.
• No invented text: silence is never transcribed, and captions Whisper tends to invent ("Thanks for watching", Amara.org subtitles) are dropped.

T3 servers update themselves

Preferences → General → T3 Code compatibility keeps each connected T3 server on the newest release of its channel (nightly stays nightly). ot3 checks T3's release list every hour and runs T3's own t3 update for the exact version, which downloads it, verifies its checksum, switches the background service to it and restarts it.

• Automatically when idle (the default) waits until no agent has worked on that server for ten minutes, since the update restarts it. Only show available updates and Off are the other choices; Update now runs it at once.
• Works on this computer and on hosts connected over SSH. A server run by the T3 Code desktop app, or not run as a background service, is explained instead of touched.
• A failed update says why and is not retried automatically for six hours, unless a newer release appears.

From T3 Code 0.1.3

• Messages from other agents fold into one line with the sending thread's title and the first line; automation messages fold the same way. Click to open one; an opened agent message links to the thread that sent it, and find opens the fold it matches.
• Thread title instructions in Preferences → General → Text generation: added to the prompt for new and regenerated titles. Projects can override them. Shown only by servers that support them.
• Compact idle threads in Preferences → General → Behavior: when the server compacts an idle Claude thread over 200,000 tokens (when you return, before the cache expires, or never). ot3 writes the mode in the form each server reads, so T3 0.1.1 clients keep reading the settings; servers from before modes do not offer Never.
• Threads are never compacted twice. When the server compacts a thread before its cache expires, globally or for that Claude instance, ot3's automatic compaction leaves it to the server and shows Compacted by the T3 server.