Release Note

OMNI Engine v0.1.2: Stress-Testing the Foundation

Early-stage software development is inherently chaotic. Features ship fast, tests are sparse, and the line between prototype and production is dangerously blurred. OMNI v0.1.2 does not introduce new capabilities — it stabilizes the ones we already had. This is the unglamorous but essential work of stress-testing every code path under real-world conditions and fixing the failures that emerge.

The Concurrent IO Challenge

The primary focus of this patch was resolving instability under heavy, concurrent terminal sessions. When multiple AI agent instances were running simultaneously — each piping terminal output through OMNI’s distillation engine — we observed intermittent buffer corruption and occasional dropped output lines. The root cause was a shared buffer pool in the IO layer that was not properly synchronized for concurrent access.

The fix involved isolating the buffer pool per-invocation, ensuring that each distillation pipeline operates on its own private memory region. This eliminated the data race without introducing any locking overhead — a critical constraint for a tool that must add zero perceptible latency to every terminal command.

Filter Capture Priority Tuning

We also adjusted the priority ordering of filter capture rules for edge cases where multiple filters matched the same input with equal confidence. The previous behavior was nondeterministic — whichever filter happened to evaluate first would claim the input — which produced inconsistent results across runs. The new behavior applies a stable, deterministic tiebreaking rule based on filter specificity, ensuring that more specialized filters always win over generic ones.

The Discipline of Patch Releases

There is a temptation in early-stage projects to bundle bug fixes into feature releases, delaying critical stability improvements until the next “interesting” version ships. We reject that approach. When we find a bug that affects production reliability, it gets its own release, its own version number, and its own changelog entry. Users deserve to know exactly when a stability issue was resolved, and they deserve the option to upgrade to the fix without also adopting unrelated feature changes. OMNI v0.1.2 is one such focused, disciplined patch.