omni

🇺🇸 English | 🇯🇵 日本語 | 🇨🇳 简体中文 | 🇸🇦 العربية | 🇮🇩 Bahasa Indonesia | 🇻🇳 Tiếng Việt | 🇰🇷 한국어

Up to 85% less tokens · Cross-Session Memory · ~40% faster · Zero hallucination triggers

Every AI coding assistant has two massive problems.

1. They read everything.
Build logs.
Docker logs.
CI logs.
Progress bars.
ANSI colors.
Thousands of tokens... to find one line. Claude isn't expensive. Your terminal is.

2. They forget everything.
Every time you restart Cursor, or switch from Claude Code to Windsurf, your agent gets amnesia. You have to re-explain the project goal. You have to remind them of the same framework gotchas over and over again.

OMNI fixes both.

The Difference

Problem 1: Your terminal drowns out the signal

npm install

Without OMNI: 10,000 lines of "Downloading...", "Extracting...", and warnings. AI reads everything.
With OMNI: Package conflict. Node 20 required.

terraform apply

Without OMNI: 4,500 lines of unchanged execution plans.
With OMNI: The 3 resources that failed IAM permissions.

docker build

Without OMNI: Endless cache hits, layer hashes, and download progress bars.
With OMNI: Missing dependency libpq-dev at layer 12.

pytest

Without OMNI: 500 passing tests and verbose setup logs.
With OMNI: Only the 2 failed assertions and their stack traces.

cargo build

Without OMNI: 300 lines of compiling dependencies and warnings.
With OMNI: The exact line where the borrow checker failed.

kubectl logs

Without OMNI: Thousands of successful health checks and normal traffic logs.
With OMNI: The crash loop and panic stack trace.

git diff

Without OMNI: Formatting tweaks, generated lockfiles, and whitespace changes.
With OMNI: Only the core business logic changes.

go test

Without OMNI: Pages of standard output from passing packages.
With OMNI: The single nil pointer dereference.

mvn package

Without OMNI: Megabytes of "Downloading from maven central".
With OMNI: Compilation error in UserService.java.

pip install

Without OMNI: Resolution logs and wheel building outputs.
With OMNI: Dependency conflict with numpy.

webpack / vite

Without OMNI: 2,000 chunk asset lists and build times.
With OMNI: Missing module resolution in App.tsx.

helm install

Without OMNI: Entire rendered YAML output of all templates.
With OMNI: Pod scheduling failure due to missing secret.

ansible-playbook

Without OMNI: "ok" and "skipped" statuses for 50 servers.
With OMNI: The single "failed" task on web-03.

GitHub Actions (CI/CD)

Without OMNI: Complete workflow logs including environment setup.
With OMNI: Only the specific step that exited with code 1.

Problem 2: Your agent forgets everything overnight

Starting a new session

Without OMNI: "Please re-explain the project structure, the auth module is broken, and we use Postgres not MySQL."
With OMNI: The agent already knows. It picks up where you left off.

Fixing the same bug twice

Without OMNI: Agent hits the same framework gotcha it already solved yesterday because it has no memory.
With OMNI: The fix is already stored. omni recall surfaces the exact solution in under 10ms.

Multi-IDE workflows (Cursor → Claude Code)

Without OMNI: New IDE, new agent, zero context. You're starting from scratch.
With OMNI: Session summary is injected automatically. New agent is immediately up to speed.

Why This Matters

The code you don't send to the AI is just as important as the code you do.

When you feed an AI megabytes of terminal noise, it suffers from context bloat—hallucinating fixes for the wrong warnings and burning your API budget on irrelevant output.

When you restart an agent and it has no memory, you lose hours re-establishing context that should have been preserved automatically.

OMNI solves both, invisibly:

• Less noise → lower cost, faster responses, zero hallucination triggers.
• Persistent memory → no more re-explaining your project, no more repeating fixes.
• One install → works silently with every agent you already use.

Benchmarks

The honest headline, measured on the release binary against 1,810 real command executions replayed from one developer's actual usage:

• 58.9% fewer bytes reaching the model across the whole mix (15.0 MB → 6.2 MB).
• 63.6% of those calls saved nothing at all. OMNI handed the output straight back, adding zero bytes. Every byte of the saving comes from the other 36.4%, where there was real noise to cut.
• Structured output is never touched. JSON, YAML, NDJSON and CSV pass through byte-for-byte, because a corrupted payload costs more than a missed compression.

That second bullet is the number most tools in this category do not print. A tool that claims to save 90% of every command is telling you it summarises output you needed.

Where the saving actually comes from, over the same 1,810 executions:

git and cargo carry the result; cat and grep are close to a no-op. OMNI earns its place on noisy, repetitive tooling output and gets out of the way everywhere else.

Single fixtures from tests/fixtures/, if you want to reproduce one by hand:

Latency is a real cost, not zero. OMNI runs on every hooked command, and the price grows with your history: a 496-byte git status takes ~82 ms against a fresh database and ~308 ms against a 97 MB one. A 16.5 KB cargo test takes ~276 ms. Budget for it.

To see your own actual token savings, just run omni stats after a few days of usage.

Quick Start & Installation

Omni is incredibly easy to set up. It natively integrates into your terminal.

macOS / Linux:

# 1. Install via Homebrew
brew install fajarhide/tap/omni

# 2. Setup Omni (Interactive Menu for Claude, VS Code, OpenCode, Codex, Antigravity)
omni init

# 3. Verify it's working
omni doctor

# 4. Or auto-fix any issues
omni doctor --fix

# 5. Check Current Status
omni init --status

Universal Installer (macOS / Linux / WSL):

curl -fsSL omni.weekndlabs.com/install | bash

Windows (PowerShell):

irm omni.weekndlabs.com/install.ps1 | iex

Integrations

OMNI works seamlessly with the agentic tools you already use. It intercepts their terminal executions automatically.

• Claude Code
• Cursor
• Windsurf
• Roo Code
• OpenAI Codex
• Antigravity CLI

Adaptive Memory OS

OMNI isn't just a terminal filter—it's a cure for AI amnesia.

If you've ever worked with an AI agent for more than an hour, you know the pain of context loss. You restart the agent, and suddenly it forgets what you were working on. It forgets the project goal. It starts making the exact same mistakes it made yesterday because it forgot the repository's undocumented quirks.

OMNI's Memory OS runs silently in the background to solve this:

• Stop Re-Explaining the Goal (omni goal): Set your North Star objective once. OMNI will relentlessly remind the agent of this exact priority on every single prompt, preventing it from drifting off-task.
• Never Lose Your Train of Thought (Session Continuity): If Cursor crashes or you switch to Claude Code, OMNI instantly injects a compressed summary of your last session. The new agent knows exactly which files were hot and what the last active error was, picking up right where you left off.
• Teach It Once (omni remember): Stop fixing the same hallucination. Agents can save project-specific rules, gotchas, and architecture decisions directly into OMNI's local SQLite backend. When they get stuck later,