A new tab, in the right place.
When directory inheritance is enabled, new tabs open in the focused tab’s working directory. WSL zsh integration reports that location automatically.
BUILT ON RIO · WRITTEN IN RUST
Keep your place when opening tabs. Read titles across languages. Let glyph memory grow as you need it. tacterm brings these changes to a terminal built on Rio.
Release 0.1.0 · Windows, macOS & Linux
01 / Windows, macOS & Linux
02 / Native x64 & ARM64 builds
03 / Open source · MIT licensed
WHAT CHANGES IN YOUR WORKDAY
When directory inheritance is enabled, new tabs open in the focused tab’s working directory. WSL zsh integration reports that location automatically.
Better shaping, font fallback, and alignment for mixed-language titles. Set a dedicated tab font and size without changing the fonts inside your terminal.
Glyph storage starts smaller and expands as more characters are used. Color glyphs grow on demand too, keeping existing characters intact.
Focused, visible maximized and fullscreen windows keep presenting, even when text is idle. This trades some idle GPU work for steady presentation; other window states remain event-driven.
These are changes in the development branch. See the release status for what ships in the current preview.
RELEASE BUILDS / 0.1.0
Download the archive for your system and processor, then follow the installation notes included inside.
Portable ZIP · Windows 10+ (x64), Windows 11 (ARM64). Requires Microsoft Visual C++ v14 Runtime. Unsigned binaries; Windows may show an unknown-publisher warning.
Microsoft runtime downloads ↗Tacterm.app · macOS 14+. Ad-hoc signed; not notarized. Gatekeeper may block the first launch.
tar.gz · glibc 2.35+ (Ubuntu 22.04+). Requires font libraries and a Vulkan-capable driver.
BEFORE YOU START
Release details and validation were reviewed 20 Oct 2026.
Read the full project statusVersion 0.1.0 and current source builds use a separate tacterm directory and import Rio settings once when that directory is absent. The earlier 0.1.0-alpha.1 preview used Rio’s configuration paths. Later changes stay independent; see the status page for migration details.
Published archives pass native build, packaging, and command-line checks on all six OS and architecture targets. Those checks do not establish graphical stability on every display or GPU. See validation results and remaining limits before relying on a preview for critical work.
It means less memory reserved for glyphs at startup. Storage grows with the characters you use and can reach the original maximum. Throughput and latency are separate measurements; we do not claim a universal speedup.
Use the Rio documentation for general configuration. For a tacterm issue, open a report on GitHub with your version, OS, GPU, and steps to reproduce it. Remove secrets from logs and configuration before sharing.
FOR DEVELOPERS
To try the development branch or contribute a fix, build from source with Rust 1.96.1 or later and the dependencies for your platform.
Source builds and downloaded releases use tacterm / tacterm.exe. Current source builds keep their settings in a separate tacterm directory and import Rio settings on first launch.
git clone https://github.com/narma/tacterm.git
cd tacterm
cargo build --locked -p riotermBuilds into target/debug/. Does not install.
WHY A FORK?
tacterm gives a focused set of fixes and experiments their own path to release, including work still pending upstream. We bring Rio improvements forward and contribute fixes back where appropriate.
That foundation is the work of Raphael Amorim and the Rio contributors. tacterm is an independent project, with its differences and validation tracked openly.