cd /news/developer-tools/llm-rewrite-of-the-terminaltexteffec… · home topics developer-tools article
[ARTICLE · art-90454] src=github.com ↗ pub= topic=developer-tools verified=true sentiment=· neutral

LLM Rewrite of the TerminalTextEffects Python

A Rust port of the Python TerminalTextEffects (TTE) library, called ttfx, delivers byte-identical frames to the original while starting in ~1 ms versus ~90 ms and achieving a median 9.6× speedup across all 37 effects, according to benchmarks from the project's CI. The parity port, created by Omacom for the Omarchy project, reproduces upstream quirks and is verified against TTE v0.15.0, with two deliberate differences: xoshiro256++ random number generation and no Python plugin support.

read3 min views1 publishedAug 10, 2026
LLM Rewrite of the TerminalTextEffects Python
Image: source

Terminal text effects as a single static binary. Pipe text in, pick an effect:

ls -la | ttfx decrypt
cat banner.txt | ttfx beams
fortune | ttfx --random-effect
git log --oneline -10 | ttfx matrix

This is a port of TerminalTextEffects (TTE) by ChrisBuilds. Every effect, the animation engine, and the command-line interface are their design — this project translates that work to Rust and adds nothing of its own to the art. If you like what you see here, star the original.

TTE is MIT licensed and so is this port; the original copyright is preserved in LICENSE and NOTICE. Please file effect ideas upstream, where they belong.

TTE is a Python package. That's the right call for a library, but for a shell toy that lives in your prompt pipeline it means an interpreter, an install step, and ~90 ms of import before the first frame. ttfx is one dependency-free binary that starts in ~1 ms.

That difference is the whole reason this exists. On a fullscreen canvas the heavier effects can't hold a high frame rate under Python:

At 200×50 cells ttfx Python TTE
beams 564 fps 71 fps
slide 5,113 fps 264 fps
waves 4,118 fps 491 fps
startup 1.2 ms 107 ms

Across all 37 effects the median speedup is 9.6× (range 4.5×–21.6×).

This is a parity port, not a reimplementation-in-spirit. Given the same input, config, and random draws, ttfx produces byte-identical frames to the Python original — verified mechanically in CI against a pinned upstream checkout (v0.15.0), not by eyeballing.

Suite Checks What it proves
tools/parity/run_suite.sh
354 every effect's frame stream, byte for byte, across configs and seeds
tools/parity/tty_compare.sh
41 the full terminal byte stream — canvas prep, cursor moves, teardown
tools/tests/cli_corpus.sh
19 exit codes and stdout/stderr routing
cargo test
goldens + traces easing/geometry/gradient values and engine state machines

Making that possible meant reproducing upstream's quirks deliberately, not "fixing" them: Python's banker's rounding, gradients built from integer floor division rather than float interpolation, a bezier arc-length approximation that drops its final segment, and looping scenes that report themselves complete on every tick. They're catalogued in plan.md; the places where Python's unordered iteration had to be pinned down are in

.

docs/ordering-inventory.md

Two deliberate differences. Random number generation is not bit-compatible with CPython — ttfx uses xoshiro256++, so --seed

is reproducible within ttfx but won't match Python's Mersenne Twister. (The parity harness swaps a shared PRNG into both sides, which is what makes frame comparison possible at all.) And Python plugin effects aren't supported, since there's no interpreter to load them.

<producer> | ttfx [terminal options] <effect> [effect options]

ttfx --help                 # all 37 effects and the terminal options
ttfx <effect> --help        # options for one effect
ttfx --random-effect        # surprise me (--include-effects / --exclude-effects to filter)
ttfx --print-completion bash|zsh

Terminal options (canvas size and anchoring, color handling, frame rate, text wrapping) go before the effect name; effect options after it. Option names and defaults match tte

, so existing invocations work with the binary name swapped.

cargo build --release
cargo build --release --target x86_64-unknown-linux-musl   # static, ~3.3 MB

Running the parity suites needs python3 and a copy of upstream:

./tools/parity/fetch_reference.sh   # clones TTE at the pinned commit
./tools/parity/run_suite.sh

Upstream is not vendored here — the harness fetches it, because it's their code.

Linux and macOS. Built for Omarchy originally; nothing targets a specific libc, and CI runs the tests and CLI corpus on both platforms. The byte-exact parity suites stay pinned to Linux/glibc — Apple's libm rounds a few transcendentals a last-ulp differently, which quantization hides in real frames but a bit-exact comparison would surface.

MIT — see LICENSE, which carries both this project's copyright and the original TerminalTextEffects copyright, and NOTICE for the attribution in full.

── more in #developer-tools 4 stories · sorted by recency
── more on @terminaltexteffects 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/llm-rewrite-of-the-t…] indexed:0 read:3min 2026-08-10 ·