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

Evidence record / pi-coding-agent

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-pi-coding-agent-mcp-1-2-0-stops-dispatching-calls-abandoned-during-oauth-refresh

MCP 1.2.0 stops dispatching calls abandoned during OAuth refresh. An HTTP tool call canceled or timed out while waiting for a shared OAuth refresh could still be dispatched after refresh completed, letting the server perform an operation the caller abandoned. A per-request signal now checks cancellation before dispatch. Shared credential refresh continues for other callers. No Pi-repository advisory was found for this repair.

Channel: tagged-release. Half: defect. Date: 2026-10-12.

Operator consequence: Upgrade HTTP MCP clients to 1.2.0 before relying on cancellation while authorization recovers. The fix does not undo an operation already dispatched to a server.

Receipt

Finding metadata

Confidence
high

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

Finding ID: 2026-10-13-pi-coding-agent-mcp-1-2-0-stops-dispatching-calls-abandoned-during-oauth-refresh

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Pi Coding Agent
    commit2026-10-13-pi-coding-agent-mcp-1-2-0-stops-dispatching-calls-abandoned-during-oauth-refreshgithub.com/earendil-works/pi/commit/da0eadf0433d29516287c7e3d7b3db325a446281tagged commit file2026-10-13-pi-coding-agent-mcp-1-2-0-stops-dispatching-calls-abandoned-during-oauth-refreshearendil-works/pi / packages/mcp/CHANGELOG.md

Versioned source: run artifact