Repository navigation
v1.16.1 — AGENTIC_NO_PROGRESS message enrichment (R2 close)
Highlights
Closes the v1.14.4-cycle followup R2 (structuredContent dropped on MCP error channel).
/6step verdict: PARTIAL TP — consumer-side rendering, not our bug. Wire format correctly preserves both structuredContent and isError per MCP spec (verified empirically — CallToolResultSchema defines them as independent optional fields). The "loss" operators saw on 2026-04-29 + 2026-04-30 benchmarks is consumer-side: Claude Code displays message-only on isError results.
Workaround we control: enrich the AGENTIC_NO_PROGRESS message string with iterations + filesRead so they're visible regardless of consumer rendering. structuredContent payload stays intact for any consumer that reads it.
Format
Before (v1.16.0):
... was repeated N times without new file reads between repeats. Returning partial state.
After (v1.16.1):
... was repeated N times without new file reads between repeats (after K iter, X files read). Returning partial state.
Tests
759 passed | 9 skipped (no count change). Regex-based pin assertions added to existing test.
Compatibility
No API/schema/code change beyond the one message-format string + 2 test assertions. structuredContent fields completely unchanged.
Install
npm install -g @qmediat.io/gemini-code-context-mcp@1.16.1