Every Command Shows Its Savings: contextzip: 200 40

After every command, ContextZip appends one line:

💾 contextzip: 8,421 → 312 chars (96% saved)

Before size → after size → percentage. You see it for every command, in real-time.

Why Visibility Matters

Most optimization tools work invisibly. You trust they're helping but you never see the numbers. ContextZip makes the savings tangible.

When you see 96% saved on your test output, you know that 8,109 characters of noise didn't enter your AI's context window. When you see 5% saved on a git status, you know that command was already clean.

Real Numbers From a Morning Session

$ npm install
💾 contextzip: 89,241 → 8,102 chars (91% saved)

$ npm run build
💾 contextzip: 12,847 → 3,412 chars (73% saved)

$ npm test
💾 contextzip: 24,891 → 1,204 chars (95% saved)

$ git status
💾 contextzip: 312 → 298 chars (4% saved)

$ docker build .
💾 contextzip: 5,621 → 841 chars (85% saved)

$ python manage.py migrate
💾 contextzip: 3,204 → 892 chars (72% saved)

Six commands, 136,116 characters of raw output reduced to 14,749. Total savings: 89%.

The git status line is honest — only 4% saved because git output is already clean. ContextZip doesn't inflate its numbers.

The Savings Line Itself

The 💾 contextzip: line is designed to be small. It adds ~50 characters to show you the savings. If the savings line itself would exceed the savings (rare edge case — very small, clean output), ContextZip stays silent.

cargo install contextzip
eval "$(contextzip init)"

GitHub: github.com/contextzip/contextzip

---

Part of the ContextZip Daily series. Follow for daily tips on optimizing your AI coding workflow.

Install: npx contextzip | GitHub: jee599/contextzip