Context runtime for coding agents

Your agent read 9,853 tokens of build log. It needed 78.

Ziver sits between Claude Code or Codex and the model and cuts the context that never needed sending: long terminal output, whole files, repeated history and tools that won't be used. It runs on your machine, and nothing you asked for is ever summarised.

$curl -fsSL https://ziveit.com/ziver/install.sh | sh
See the numbers

Works with Claude Code · Codex · macOS, Linux and Windows

./gradlew assembleDebug
Without Ziver406 lines · 9,853 tokens
With Ziver78 tokens · 99% less
[12 lines omitted]
[and 378 more lines of the same shape]
e: file:///work/app/src/main/kotlin/com/example/auth/AuthRepository.kt:92:17:
   type mismatch: inferred type is Token? but Token was expected
[2 lines omitted]
> Task :app:compileDebugKotlin FAILED
[10 lines omitted]
BUILD FAILED in 1m 12s

[ziver] 78 tokens instead of 9,853 (99% less)
[ziver] the original is at ctx://blob/odhxpmfg6aipw

How it works

Six ways to spend fewer tokens

Each one works on a different part of the agent's job. The numbers are measured, not estimated.

Terminal output

Builds, tests and linters return only errors, failures and status. The rest stays available if the agent needs it.

97%fewer tokens on builds and tests

Code on demand

The agent asks for the function it needs, not the whole file. The index keeps up as you edit.

98%less than reading the whole file

The right context for each task

Understands what the request requires and sends only what the task needs, within a budget.

99%less context per task

Safe compression

Every cut is checked. If it would lose a requirement, a number or a negation, the original is sent instead.

95%less, without losing any of your instructions

Session memory

When the conversation is compacted, the agent still knows the goal, the constraints and what was already ruled out.

98%less context to resume a long session

MCP tools

Your MCP servers stay available, but each tool's definition is loaded only when it is about to be used.

99%fewer tokens, even with hundreds of tools

The numbers

Fewer tokens, without giving anything up

up to 99% fewer tokens sent to the model
0 of your instructions lost or reversed
< 2 ms of added wait per request
0 lines of your code sent to Zive IT

Measured on builds, tests, long sessions and MCP servers. Savings vary with the project and the way you work.

Guarantees

What Ziver never does

Summarise what you asked for

Your instructions and constraints reach the model exactly as you wrote them.

Lose the original

Everything removed is kept and can be recovered at any time.

Send credentials

Detected passwords and keys stay on your machine, whatever the settings. Your code leaves only if you allow it.

Block your agent

If anything goes wrong with Ziver, the agent keeps working normally without it.

Touch your config without a backup

Shows every file before changing it, keeps a copy, and undoes everything with a single command.

Install

Two minutes, three commands

  1. Get the binary

    $curl -fsSL https://ziveit.com/ziver/install.sh | sh

    Detects Apple Silicon or Intel, verifies the SHA-256 and installs to ~/.ziver/bin, without sudo.

  2. Sign in

    $ziver login

    Opens your browser to sign in with email, Google or Microsoft and connect this machine. Every plan, the free one included, uses an account. Each machine gets its own access.

  3. Connect your agent

    $ziver init && ziver setup claude

    Connects Ziver to every Claude Code profile on this machine (for Codex, use ziver setup codex). Restart your agent and type /ziver in a session to see its status and savings; /ziver-disable and /ziver-enable turn it off and on for that session only.

Pricing

Prove the saving before you pay

Community is free, and complete enough to measure what Ziver saves in your real workflow.

 

Community

Free
  • Up to 1 million tokens saved a month
  • Local repository indexing
  • Symbol-level code retrieval
  • Terminal output compression
  • MCP gateway
  • API proxy, with provider-reported usage
  • Session memory
  • Fidelity checks on every compression
  • Claude Code and Codex
  • Online savings dashboard
Install

Recommended

Pro

$120/year
  • Up to 10 million tokens saved a month
  • Everything in Community
  • Aggressive compression mode
  • Automatic context budgeting
  • Local auxiliary models
  • Multiple repositories
Subscribe

 

Power

$290/year
  • Up to 50 million tokens saved a month
  • Everything in Pro
  • Cross-repository retrieval
Subscribe

5 seat minimum

Team

$240/user/year
  • Up to 50 million per user, a month
  • Shared policies
  • Team analytics and cost reporting
  • Central management and admin dashboard
  • SSO
Subscribe

 

Enterprise

Custom
  • Unlimited tokens
  • SAML · SCIM
  • Private cloud or on-premise
  • Audit logs
  • Zero-retention controls
  • Support SLA
Contact sales

Start free. When the month's limit is used, Ziver pauses until the next month and your agent keeps working normally, just without the savings. Change plans whenever you like, from your dashboard.

Questions

What people usually ask

Does my code leave my machine?

No. The index, compression, memory and gateway run locally, and no code, file, command or output is sent to Zive IT. To show your dashboard, Ziver sends numbers only: how many tokens it saved per day and kind, and the name and system of each connected machine. Detected credentials never leave, whatever the configuration.

Does the model answer worse?

No. Ziver only removes what it can show does not change the request, and everything it removes stays recoverable.

Which agents work?

Claude Code and Codex are fully integrated through ziver setup. Any agent that speaks MCP can use Ziver's server directly.

How do I undo everything?

ziver setup claude --undo restores every configuration file exactly as it was. After that, deleting ~/.ziver removes the rest.