Tokmizer 1.1.1

Tokmizer 1.1.1: we now know which install channels work, and our numbers no longer shrink.

What's new

• Install channel. On sign-up the plugin also sends one word for how it was installed: Claude Code, Codex, npm, npx, Homebrew or the install script. It is read from where the plugin runs. Nothing about your machine or your commands.
• What usage stats are for. They keep only command names and token counts, never command contents, arguments, output or files. We use them to spot when compression gets worse or something breaks, and fix it before it reaches everyone. tkr telemetry off still stops them.

Install or update

• Claude Code: /tkr-update, or /plugin marketplace add norwelltw/Tokmizer then /plugin install tokmizer@tokmizer
• npm: npm i -g @tokmizer/plugin@1.1.1
• Homebrew: brew upgrade tokmizer
• Standalone (macOS, Linux): curl -fsSL https://tokmizer.com/install.sh | bash

Checked at the release commit: full test suite with PostgreSQL, migrations, compression quality and fidelity benches, Rust engine and launcher, 22 upgrade scenarios, public source export scan, Linux arm64 and x64 smoke tests, site build and Playwright audit.

Tokmizer 1.1.0

Tokmizer 1.1.0: nothing about your machine leaves it, 15 devices, a patched Node.js.

What's new

• No machine details. The plugin now sends only a random install ID, its hash, your time zone and the plugin version. Computer name, OS and version, CPU, and the hashes of the network card address and user name are no longer read, sent or stored, and the stored values were deleted.
• 15 devices. One license covers up to 15 connected devices at once, with no lifetime limit (it was 3 at once and 8 in total). Devices already linked keep their place.
• Patched Node.js. Installing with npm needs Node.js 24.22.1+, 22.23.4+ or 26.12.1+, the releases with the October 21, 2026 security fixes. Node.js 20 is end of life.

Install or update

• Claude Code: /tkr-update, or /plugin marketplace add norwelltw/Tokmizer then /plugin install tokmizer@tokmizer
• npm: npm i -g @tokmizer/plugin@1.1.0
• Homebrew: brew upgrade tokmizer
• Standalone (macOS, Linux): curl -fsSL https://tokmizer.com/install.sh | bash

Checked at the release commit: full test suite with PostgreSQL, migrations, compression quality and fidelity benches, Rust engine and launcher, 22 upgrade scenarios, public source export scan, Linux arm64 and x64 smoke tests, site build and Playwright audit.

Tokmizer 1.0.2

Tokmizer 1.0.2: a complete README.

What's new

• One README for npm and GitHub. A before/after example, the 2026-10-19 benchmark against rtk 1.0.1, install for every channel, the 21 supported agents, Claude Code permission modes, every command, compression modes, restore, gain, custom rules, rtk migration, CI, and exactly what leaves your machine.
• No change to the CLI, hooks, engine or rules since 1.0.1.

Install or update

• Claude Code: /tkr-update, or /plugin marketplace add norwelltw/Tokmizer then /plugin install tokmizer@tokmizer
• npm: npm i -g @tokmizer/plugin@1.0.2
• Homebrew: brew upgrade tokmizer
• Standalone (macOS, Linux): curl -fsSL https://tokmizer.com/install.sh | bash

Checked at the release commit: full test suite with PostgreSQL, compression quality and fidelity benches, Rust engine and launcher, upgrade scenarios, public source export scan, and Linux arm64 and x64 smoke tests.

Tokmizer 1.0.1

Tokmizer 1.0.1 — Claude Code installs get their rule updates again.

What's fixed

• Rule updates on Claude Code. Since 0.9.59, an install used in Claude Code's default permission mode never registered with tokmizer.com, so it kept the rules shipped in the package and never heard about new versions. It now registers on its first session, after the network notice, and retries at each session start and after a command until it succeeds. tkr network off still blocks every connection.

Install or update

• Claude Code: /tkr-update, or /plugin marketplace add norwelltw/Tokmizer then /plugin install tokmizer@tokmizer
• npm: npm i -g @tokmizer/plugin@1.0.1
• Homebrew: brew upgrade tokmizer
• Standalone (macOS, Linux): curl -fsSL https://tokmizer.com/install.sh | bash

Checked at the release commit: full test suite with PostgreSQL, compression quality and fidelity benches, Rust engine and launcher, upgrade scenarios, public source export scan, Linux arm64 and x64 smoke tests, and a fresh install from the packed release that registers on its first session.

Tokmizer 1.0.0

Tokmizer 1.0.0 — free, with no plans.

What's better

• Nothing important gets cut. A failed test run keeps every assertion and its location, an error line in the middle of a long log stays in the summary, and output that could not be saved for tkr restore is delivered whole. Images pass through untouched.
• Faster hooks. When the Tokmizer server is slow to answer, a command now waits about 0.45 s instead of 3 s; a leftover daemon lock costs 0.45 s instead of 8 s.
• Very long lines and commands are handled in linear time, so a huge single-line output no longer slows a session down.
• Smoother setups. Repairing the Codex config.toml and removing the Mistral Vibe hook only touch Tokmizer's own entries; read-only config files are left alone; the optional PATH line is written atomically.
• Your admin's rules come first. Command rewriting follows Claude Code policies delivered from the claude.ai console, MDM, the Windows registry or WSL.
• Shims run the real command directly when one is copied or linked elsewhere on your PATH, and pass terminal hang-ups on to it.
• Windows: commands are looked up on PATH only.
• Updates. The standalone binary checks the signed SHA256SUMS before updating, and command and skill bundles are versioned, so an installed command is never replaced by an older text.
• Free for everyone. Every mention of paid plans is gone, and suggestions and learning work the same on every install.

Install or update

• Claude Code: /tkr-update, or /plugin marketplace add norwelltw/Tokmizer then /plugin install tokmizer@tokmizer
• npm: npm i -g @tokmizer/plugin@1.0.0
• Homebrew: brew upgrade tokmizer
• Standalone (macOS, Linux): curl -fsSL https://tokmizer.com/install.sh | bash

Checked at the release commit: full test suite with PostgreSQL, compression quality and fidelity benches, Rust engine and launcher, 22 upgrade scenarios, public source export scan, Linux arm64 and x64 in containers, site build and audit. Windows and Intel macOS builds were cross-compiled but not run.

Tokmizer 0.9.72

• Shorter ls -l listings: the permission string shared by most directories and the one shared by most files are written once in the summary; an entry whose mode differs (an executable, a link) keeps it on its line. Names, directory markers, sizes, modes and owners all stay readable. On the ls -la output of the comparison corpus: 795 characters instead of 1,288 (rtk 1.0.1: 919).
• Two release-check tests made reliable on a loaded machine.

Checked locally at the release commit (full test suite with PostgreSQL, fidelity and quality benches, Rust engine and launcher, upgrade safety, public source export scan, Linux arm64/x64 in containers, site build and audit). Windows and Intel macOS builds were cross-compiled but not run.

Tokmizer 0.9.71

• Claude Code worktree sessions: in a linked git worktree, commands that mention git run as typed, so the worktree isolation check never refuses them; their output is still shortened after the run.
• Privacy: the session log masks tokens and passwords in commands.
• Reliability: an output too large for tkr restore says so; a write error on Tokmizer's own output no longer replaces the command's exit code; CLAUDE_CONFIG_DIR=~/… is expanded.
• Windows command names reach their filters (python.exe -m pytest, pytest.exe, py -m pytest, npm.cmd test, dotnet.exe test); deno prints deno: ok when it succeeds silently.
• tkr gain: --json adds allCommands and shortenedOnly, each with its own counts and rate; usage events dropped by a full local queue are counted and shown.
• Site: unknown addresses return a server-rendered 404 page.

Checked locally at the release commit (full test suite with PostgreSQL, fidelity and quality benches, Rust engine and launcher, upgrade safety, public source export scan, Linux arm64/x64 in containers, site build and audit). Windows and Intel macOS builds were cross-compiled but not run.

Tokmizer 0.9.70

We read the 482 open bug reports of rtk, checked each bug class against Tokmizer and fixed every class Tokmizer shared, each with a test.

• Commands keep working as typed: dev servers and watchers (npm run dev, next dev, vite, tsc -w, docker compose up, tail -F, turbo dev, nx serve…) run as typed so their output shows up live; { …; } > file, loops and if blocks writing to a file or a pipe are left whole; a command that leaves a process in the background returns as soon as it exits; signal exit codes match the shell's.
• Outputs keep what matters: no "ok" or "no changes" when the command failed or ran quietly; sorted ls listings keep their order and dates; grep, curl, python, cargo run and dig outputs keep their content; git -C <dir> reaches the right filter and patches keep their context lines and trailers; restore pointers never glue onto the next output.
• Hooks and settings: only hooks Tokmizer wrote are recognised as Tokmizer's, so a user hook that calls tkr is never removed; settings files with a byte order mark are read correctly.
• Site: two-column hero, tighter home sections.

Checked locally at the release commit (full test suite with PostgreSQL, fidelity and quality benches, Rust engine and launcher, upgrade safety, Linux arm64/x64 in containers, site build and audit). Windows and Intel macOS builds were cross-compiled but not run.

Tokmizer 0.9.69

• rtk's newest commands: ctest, phpstan (JSON report), bun test, deno test, ./gradlew, mvn and mvnd outputs are shortened. Failing tests, their messages and their own frames are always kept.
• Default mode in Claude Code: build and test commands your rules do not already allow are shortened before they run, with the one prompt Claude Code would show anyway. Deny and ask rules still apply; read-only commands are not touched.
• Fail-open launcher: these commands go through ~/.tokmizer/bin/tkr-run, which runs the original command, with its exit code, whenever Tokmizer is missing or cannot run.
• Safety: a shortened output is never longer than the original, and Windows line endings are read correctly.

Checked locally at the release commit (full test suite with PostgreSQL, fidelity and quality benches, Rust engine and launcher, upgrade safety, Linux arm64/x64 in containers, site build and audit). Windows and Intel macOS builds were cross-compiled but not run.

Tokmizer 0.9.68

• Shorter git and wc outputs: git log shows one line per commit with its subject (the rest stays restorable), git status uses git's short format, and wc states a shared folder once.
• Two figures in tkr gain: savings on every command, and savings on the outputs Tokmizer shortened.
• Faster hooks for plugin catalog installs: the native launcher is switched on at the next session after a check of its checksum and version; Node stays as the fallback.

Checked locally at the release commit (full test suite with PostgreSQL, fidelity and quality benches, Rust engine and launcher, Linux arm64/x64 in containers, site build and audit). Windows and Intel macOS builds were cross-compiled but not run.