You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Default MCP responses remain in compatible mode for text-only clients. Hosts that consume structuredContent can add --result-content=deduplicated to the existing server arguments,
then reconnect MCP. Ordinary tool calls automatically remove duplicate JSON text echoes;
agents do not need to run a filter or call another tool. Unique content and structured data
remain available, and tool counts stay at 14 typed tools or five toolbox tools.
Result size measurements are UTF-8 bytes, not model-token counts. This release does not claim
a measured reduction in host token billing.
Added
--result-content=deduplicated automatically removes equivalent plain JSON text echoes from
ordinary MCP replies after SDK processing, for typed/toolbox surfaces over stdio or HTTP.
It preserves structured values, unique/annotated content, exact numbers, errors, approvals, and
metadata, and updates typed text-byte measurements. No extra tool or filter call is needed.
The default compatible mode retains text-only client behavior; structured-aware hosts opt in
through startup arguments. Initialization reports the active mode. Tool counts are unchanged.
repoplane render-result filters one captured MCP result from stdin for client-wrapper
development. It preserves unique or annotated content, exact numbers, errors, approvals, and
metadata, with a 16 MiB input limit. Ordinary MCP calls in deduplicated mode do not need it.
Changed
MCP initialization guidance and typed/toolbox operation descriptions now distinguish registered
capabilities, background records (including saved code/design), and present source inspection.
Memo current means active; current-code claims require checking evidence and invalidation. payload_fields guidance includes examples and states that it selects top-level fields only.
Fixed
The Windows Runner batch test fixture explicitly emits UTF-8, so its Unicode argument check
no longer assumes that the host OEM code page is UTF-8. Runner output bytes are unchanged.