Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Finding / grok-build

2026-10-13-grok-build-http-mcp-json-rpc-errors-no-longer-cause-repeated-tool-execution

HTTP MCP JSON-RPC errors no longer cause repeated tool execution. The vendor documents a duplicate-execution correction on the HTTP MCP error path. A reported error in an older affected build was not assurance that a side-effecting tool ran zero or one times.

Channel: tagged-release (stable 1.0.52). Half: defect. Date: 2026-10-11 (1.0.52 note).

Operator consequence: Upgrade side-effecting HTTP MCP workflows to 1.0.52 and test an error-after-action case. Keep service-side idempotency keys and an action ledger where repeats are costly; this narrow client correction does not establish exactly-once delivery across disconnects or other retries.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-grok-build-http-mcp-json-rpc-errors-no-longer-cause-repeated-tool-execution

Profile citations

  • grok-build / claim / http-mcp-error-single-execution

Source links

Primary links, including exact changelog lines when available.

  1. Grok Build
    official docs2026-10-13-grok-build-http-mcp-json-rpc-errors-no-longer-cause-repeated-tool-executionstorage.googleapis.com/grok-build-public-artifacts/cli/changelogs/1.0.52.external.md