Ai

Oh-My-OpenAgent v4.7.4: LazyCodex Context Cleanup Stabilized

Oh-My-OpenAgent v4.7.4: LazyCodex Context Cleanup Stabilized

Oh-My-OpenAgent’s latest patch, v4.7.4, pushes the LazyCodex context cleanup from the previous release into a production-ready state. This isn’t just a routine hotfix — it’s a deliberate stabilization that makes the tool safer for everyday use.

What Changed

The LazyCodex cleanup logic, introduced in v4.7.3, has been hardened to prevent memory leaks and context corruption. The release also tightens the rules source selection to match the current agent-doc policy, meaning the system now correctly picks the right rule set when multiple are available. On the distribution side, the Codex component bundle is now building cleanly for both npm and the marketplace — no more broken dependencies or missing modules.

Perhaps the most practical improvement is the clean install path. The root package, platform package, and Bun lockfile are all version-matched, so you can run bun install --frozen-lockfile without surprises. This also extends to npm wrapper installs and LazyCodex local installs. For a tool that relies on consistent dependency resolution, this is a big deal.

Why It Matters

Context management is the Achilles’ heel of many AI agent frameworks. By stabilizing LazyCodex’s cleanup, Oh-My-OpenAgent reduces the risk of stale context bleeding into subsequent interactions. That’s critical for developers building multi-step agent workflows. The alignment of rules source selection with agent-doc policy also means fewer “why did my agent suddenly change behavior?” moments.

And from a DevOps perspective, the clean install path eliminates a common pain point. I’ve personally wasted hours debugging mismatched lockfiles in multi-package repos. This fix alone could save teams significant time — and headaches.

Official Source: https://github.com/code-yeongyu/oh-my-openagent/releases/tag/v4.7.4