Omarchy T3 Code v0.2.24

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

One-step install on a fresh machine

• The installer now sets up T3 Code nightly itself when it is missing (t3code-nightly-bin, from Omarchy's repository or the AUR through yay/paru) and opens it once so T3 creates its profile. The local backend then runs as T3's own service, so it keeps running when no T3 window is open. On a terminal, the installer asks whether to open T3 Code afterwards.
• A failing step is named instead of the installer stopping silently, and curl | bash never runs a partially downloaded script.

Agent memory

Preferences → General → Agent memory releases idle agent sessions after five minutes by default, with a global timeout and per-environment or per-provider overrides, including Never. The conversation resumes on the next message.

Lighter desktop UI

Menus, utility pages, review controls, model-picker contents and video playback load only when used, long discarded histories are reclaimed, and the graphics texture atlas is much smaller. Measurements are in docs/UI_MEMORY.md.

Fixes

• The panel opens under the bar on Omarchy versions whose bar spans the whole screen, instead of at the bottom of the screen.
• After T3's profile is recreated, ot3 issues a new local credential instead of staying unauthorized.
• Updating a checkout pinned to an annotated release tag no longer fails with "Binary and source revisions differ".
• Multiplexed SSH forwards keep their owner, and connection failures show a persistent reason.
• A global animations switch, sidebar selections revealed in the mosaic, and Ctrl+B visibility separated from Super+B focus.

Omarchy T3 Code v0.2.23

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

Thread mosaic

Watch 1 to 8 threads live side by side. Each tile shows its phase with its own color and motion: T3's working blue while an agent thinks, reads, edits, runs or answers; a distinct tone when it waits for you, fails or finishes. Tiles keep their slots, page with a flip, can be filtered, and follow streamed text like the chat until you scroll up.

Quick replies

A quick replies button in the composer sends your saved answers in one click. The list is configurable in Preferences.

Host filter and fuzzy sidebar search

• Host filter: show only the threads of one machine.
• Fuzzy search ignores accents, case and word order, tolerates typos, matches host names and finds messages on the server. The sidebar stays put when nothing matches.
• Sidebar lists scroll by wheel or touchpad only, so a click is never swallowed by a drag.

Dictation keeps long recordings whole

• Dictations longer than 25 seconds are split at natural pauses and transcribed piece by piece, so a several-minute dictation comes back complete instead of truncated.
• Each recording and its text are kept per thread. Rest the mouse on the microphone to play, delete or open them. Preferences → Dictation → Keep recordings sets how long they stay; they go when the thread is archived or deleted.

Fixes

• Git failures such as "Author identity unknown" or "Authentication failed" now show git's reason instead of a missing-permission message; a real missing permission names the scope it needs.
• Client activity reports reach the server again, and importing sessions without a project no longer fails.
• All T3 traffic now goes through the shared T3 protocol library.

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.

Omarchy T3 Code v0.2.20

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.

Fixes

• Stale QML and integration test contracts were brought up to date, and a binding loop one of them found is fixed.

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)

5606c7b99a9996533542793ad8153bd4862707e328342f08a86ee942315bd5bf  omarchy-t3-code-v0.2.20-linux-aarch64.tar.gz
f87b8b88b3f9af0b89c62c4a7c23e076df4ce2e0e81548cacfe6e0d13c2a4e47  omarchy-t3-code-v0.2.20-linux-x86_64.tar.gz

Omarchy T3 Code v0.2.19

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

Omarchy T3 Code v0.2.18

Native aarch64 and x86_64 packages for Omarchy on Arch Linux, with the Rust client, the Qt HTML preview frontend and the new QML preview renderer. Install or update with the README one-liner:

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

Highlights

Native QML previews

When the agent answers with a qml code block, the finished message shows the running component in the block's place instead of the code:

• A bar above each block switches to the code, copies it and opens the preview in a window.
• While the answer is still streaming, the code is shown. The preview appears once the block is complete.
• With Preferences > HTML renders > Side panel, each block becomes a card for the Renders tab, and new QML answers open there on their own, like HTML pages.
• Components get the Omarchy theme: omarchy.background, foreground, accent, surface, muted, red, green, yellow and blue, and Qt Quick Controls follow the same palette.
• Compile and runtime errors are listed inside the preview, with line and column.

Locked down to previewing

Agent-written QML never runs in the shell. Each preview runs in its own small Qt Quick process (no WebEngine), with several independent layers:

• Imports: only QtQuick, QtQuick.Controls, QtQuick.Layouts, QtQuick.Shapes, QtQuick.Effects and QtQml. Anything else, including Quickshell, Quickshell.Io, QtCore, QtQuick.LocalStorage and file or directory imports, is refused with a clear message before Qt starts. Imports inside Qt.createQmlObject strings are checked too.
• Qt engine: a private import path that only contains those modules, a network layer that fails every request, a URL filter that refuses files outside them, and links that open nothing.
• Process: an empty environment (no tokens, D-Bus or display), no PATH, lower priority (nice 10) and a 512 MiB heap limit.
• Kernel: a Landlock domain. The renderer can only read Qt, system libraries and fonts, can only write its frame directory, cannot open TCP connections and cannot start any other program.
• Watchdog: a component stuck in an endless loop is closed after 4 seconds, and the preview says so.

A preview uses 25–85 MB in a single process, compared with about 150–240 MB over five processes for an HTML page. Animations are captured at up to 20 frames per second as uncompressed frames in memory, which costs about 2% of a core in the renderer.

Synced with T3 Code 0.1

This release follows the T3 Code 0.1 nightly (v0.1.1-nightly.20261020.3386):

• Protocol: a live shell subscription per environment keeps the sidebar current, archive confirmations, and the new thread events (pull request links, detached sessions, background work, context handoffs and MCP apps).
• Composer: effort shortcuts, a branch picker (switch, create, adopt or restore), worktree setup progress, a context window meter, a subagent bar with stop and workflow scripts, quoting a selection from a response, and sender attribution for automation and agent messages.
• Threads: a command palette (Ctrl+K) with message search across every thread, fork from a response, merge back, reorder pinned threads, thread links across environments, and notification sounds.
• Conversation: secret requests, MCP apps, Mermaid diagrams, LaTeX math, copying tables as Markdown or CSV, HEIC/HEIF/AVIF attachments, and a command's live output in the tool inspector.
• Pull requests: merge, close, reopen, ready and draft, comments, reviews, reviewers and labels, and opening a pull request in a thread or a worktree.
• Pages: usage (cost, tokens, sessions, prices), scheduled tasks, Claude and Codex session import, process diagnostics with resource history, storage cleanup, provider install, sign-in and update, ACP registry agents, telemetry export endpoints, discovered dev servers, device settings, and Initialize repository.

Fixes

• A lighter shell. Loading spinners could leave the shared animation clock running at 60 fps for the rest of the session, so the panel kept redrawing even when nothing moved. With one HTML or QML preview on screen the shell now idles at about 1.5% CPU instead of 6–8%.
• Remote environments with delegated tasks connect again. Thread ids that contain a dot (for example a delegated task named upload-1.2) made the whole environment look disconnected.
• Settings writes no longer report a false settings_write_dropped.
• The sidebar language picker and the provider name in the model label are gone.

Notes

• Any QML component you want to preview can use omarchy.* for colours; a fixed-size root is centred, an unsized one fills the preview.
• Diagnostics and measurements are in docs/DEVELOPMENT.md.

Checksums (SHA-256)

8297fc51f237104d499515621ba15a85da4b9f8d75f9d0f17703e087f45b3f71  omarchy-t3-code-v0.2.18-linux-aarch64.tar.gz
a446b20b87b062e1a9c7df58cdb16a38ae83e8a9f09397e5e76e8b25a35fddb7  omarchy-t3-code-v0.2.18-linux-x86_64.tar.gz

Omarchy T3 Code v0.2.17

Native aarch64 and x86_64 packages for Omarchy on Arch Linux, with the Rust client and the Qt HTML preview frontend. Install or update with the README one-liner:

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

This release follows v0.2.15 (v0.2.16 was tagged but never published).

Highlights

Multi-purpose side panel

The panel next to the chat is no longer just a browser. The new side panel button opens tabs for:

• Browser: the preview browser, as before.
• Renders: HTML pages the agent renders in the chat, with a picker when there are several. Preferences can send new renders here instead of showing them inline.
• Devices: simulators and emulators from T3 Code (see below).

All tabs share one resizable slot. In narrow windows the panel opens as a sheet over the chat. omarchy-shell io.github.avillagran.omarchy-t3-code sidePanel <browser|renders|devices> opens a tab from scripts or keybindings.

Simulators and emulators from T3 Code

The Devices tab connects to T3 Code's device support:

• It lists the simulators and emulators on your T3 environment's device hosts. Opening the tab refreshes the list, which installs or starts the device hub when needed, as in the T3 web app.
• Start/Open boots the device for the current chat and shows its screen in the panel. You can tap and swipe with the mouse, use the hardware buttons (Back, Home, Recents, Power) and type.
• Close only stops viewing. Power off ends the session and shuts the device down.
• iOS uses the simulator's MJPEG stream. Android decodes the emulator's H.264 stream with ffmpeg when it is installed, and otherwise falls back to periodic screenshots.

Tested against a live Android 14 emulator on a remote T3 environment.

Smooth, adaptive animation

• One shared clock. The sky, spinners, the working shimmer and thread comets all run on one clock, so their frames coincide instead of adding up. Each animation runs only as fast as it needs: the idle sky drifts slowly, spinners and comets run at 60 fps, and shooting stars run at the display rate only while one is on screen.
• Preferences > Animations > Animation smoothness offers Adaptive (default), Saver (30 fps) and Maximum.
• Threads changing section fly to their new place. When a thread moves between Working, Ready, Snoozed and Settled, it travels there and the rows around it slide out of the way. The motion style (Swoop, Glide, Fade or Off) and its speed are configurable.
• Smoother indicators. The spinner is now a continuous arc, the "working" shimmer sweeps continuously, and the draft saved/saving state cross-fades. The thread state icons animate when they change.
• Bar indicator styles. Choose Orbit, Scanner, Equalizer, Heartbeat, Ticks or Living logo. The indicator is coloured by error, pending question or work, and moves only while a thread works. The bar no longer redraws at the display rate.
• Frame rate meter (Preferences > Animations). It separates ambient motion from real drops.

Faster scrolling and streaming

• Streamed messages no longer re-serialise the whole conversation on the UI thread: about 0.7 ms per update instead of about 7.9 ms on a long chat.
• Conversation rows build only the card they show. Each row was about three times slower to create, and its hidden cards re-ran their bindings on every scroll frame.
• The detached window uses an opaque surface on opaque themes, so Hyprland skips drawing and blurring what lies behind it.
• Keyboard shortcut resolution is cached per focus state.

Fixes

• New chats inherit the permissions of the chat that is open. The project default no longer overrides them.
• HTML renders that arrive while a chat is open now appear. Before, they only showed after reloading the chat.
• Device state from T3 with empty optional fields no longer fails as invalid once device support is turned on.

Notes

• ffmpeg is optional. It only makes Android emulator screens smooth.
• On device hosts, start the T3 server with a modest open-file limit, for example ulimit -n 524288. With a very large limit, which an SSH-launched server can inherit, the Android emulator hangs and crashes before it comes online.
• Diagnostics: profileScroll, profileResult and skyState IPC commands (see docs/DEVELOPMENT.md).

Checksums (SHA-256)

187d7861c7f0fb50155553f538ef06094643218ca0801c685452e34f48165cde  omarchy-t3-code-v0.2.17-linux-aarch64.tar.gz
194eb6492f757e250c073100433babfc51f041ecf072402f538fbaa2569a649a  omarchy-t3-code-v0.2.17-linux-x86_64.tar.gz

Omarchy T3 Code v0.2.15

Native aarch64 and x86_64 packages for Omarchy on Arch Linux. Includes the Rust client and Qt HTML preview frontend. Install or update using the README one-liner.

Omarchy T3 Code v0.2.14

Native aarch64 and x86_64 packages for Omarchy on Arch Linux. Includes the Rust client and Qt HTML preview frontend. Install or update using the README one-liner.

Omarchy T3 Code v0.2.13

Native aarch64 and x86_64 packages for Omarchy on Arch Linux. Includes the Rust client and Qt HTML preview frontend. Install or update using the README one-liner.