v0.1.6 — Indexing progress and automatic retry

Pending index synchronization now returns a normal updating status in MCP instead of appearing as a search failure. The response makes clear that search has not run yet and includes the available indexing progress.

• Report parsing, embedding, and finalization stages, with completed/total documents requiring new vectors during embedding.
• Retry a pending MCP search once, waiting up to 10 additional seconds (40 seconds of synchronization waiting by default). Set freshnessWaitMs: 0 to disable waiting and retry.
• Keep actual indexing failures and source changes during retrieval as explicit errors. Stale source is never substituted.

Update

npm install -g open-context-engine@0.1.6

Reconnect your MCP client after updating to load the new behavior. If indexing is still pending, check index_status for the same project and retry search_code once ready.

Validation

• All 68 Node tests and 61 Python tests passed locally, with no skipped tests.
• Linux, macOS, and Windows platform checks passed for release commit 014b3eaa5613f720dddf7aaa00dc22146ed03042.
• The exact archive passed isolated installation, both CLI aliases, fresh Python setup, doctor, and real-model MCP retrieval, including project switching, saved edits, file deletion, and restart recovery.
• npm reports latest=0.1.6; published integrity and a clean registry installation match the verified archive.

The exact npm archive and its SHA-256 checksum are attached.