Ai

LazyCodex 4.7.5 Patches LSP MCP Dependency Packaging Hole

LazyCodex 4.7.5 Patches LSP MCP Dependency Packaging Hole

LazyCodex AI has shipped a tiny but critical patch. Version 4.7.5 fixes a packaging hole that broke fresh installs for users relying on its bundled LSP MCP component. The issue? A missing package.json inside the published tarball. Without it, new setups couldn't resolve the dependency and failed silently. Not anymore.

What Changed

The release notes pinpoint the culprit: packages/lsp-tools-mcp/package.json was absent from the tarball of the previous release. That single file carries the manifest for the LSP MCP plugin — a critical piece for code intelligence features. The fix was straightforward: include it. The team verified that a fresh install now works via a headless command: lazycodex-ai@latest install --no-tui --skip-auth successfully creates the expected node_mod directory.

Why It Matters

This isn't a flashy feature drop. But reliability patches like this prevent early adopter frustration. For developers evaluating LazyCodex, a busted first install can kill trust. The fix ensures that the onboarding experience matches the promise: zero friction. That's the kind of attention to detail that separates tools from toys. And it's a reminder that even a missing JSON file can derail an entire workflow. Now it's back on track.

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