Omni

The interesting thing about OMNI is what it refuses to do. It will not compress a command that exits non-zero. It will not touch JSON, YAML, NDJSON or CSV — those go through byte-for-byte, because a corrupted payload costs more than a missed compression. A distiller that parses no signal hands back the raw output rather than writing a green "no errors" line nothing supports. Those constraints are written down as outranking compression, in that order, every time they conflict, and they're the reason you can leave it on for everything. The mechanism worth understanding is the split between filters and the ledger. Filters remove a line because a pattern calls it noise — that's the half every tool in this category can do. The ledger removes a line because your agent is already holding it. On the vendored corpus, 68.4% of raw bytes were lines the agent had already been shown, and 64.7% still were after every distiller ran. The second read of a file costs 214 bytes instead of 7.6 KB. That's a property of the mechanism, so it reproduces on any machine; the corpus-wide 69.6% is a property of the corpus, which OMNI says plainly. The costs are real and disclosed. 1 in 26 commands is touched at all; the other 96.1% are handed back with zero bytes added, so for a workload where every file is read once you are paying latency for nothing. That latency runs 21 ms against a fresh database and 61 ms against a 205 MB one for a 496-byte git status — the cost grows with your history, not with the payload. Budget for it on a large store. Beyond distillation there's a memory layer: omni recall pulls a stored fix back before the agent repeats a mistake, omni goal restates the objective on every prompt to stop drift, omni doctor prints which support tier each installed host actually gets, and omni stats reports what OMNI did on your own history in counted bytes. Support differs by host, which is worth checking before you plan around it. The honest comparison set is other local token-saving shell wrappers, not GUI context tools. OMNI's distinguishing bet is the handle-and-retrieve model plus a project-keyed store that crosses both sessions and agents. The counterweight is that a handle is only valid while the agent can still hold the original lines: when the context window compacts, OMNI deliberately forgets what it had shown, and it cannot stop a compaction. Handles older than the 30-day rolling window won't resolve either, and inputs above the 64 KB archive cap aren't archived at all — the marker says so, with the size. That's the shape of the trade: big savings on repeat-heavy repos, nothing on one-shot workloads, and a hard expiry on the recall you build up.