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-a-starting-session-is-busy-during-before-agent-start-in-1-2

A starting session is busy during before_agent_start in 1.2.0. During before_agent_start, isIdle is now false, sendMessage queues into the starting run, sendUserMessage requires deliverAs, and an abort during startup is honored when the run starts. Custom-message runs also retain handler-added prompt sections rather than removing them after their first tool call and breaking the prompt cache.

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

Operator consequence: Migrate extensions that send messages during startup, not only their user/custom event typing. Test explicit delivery choices rather than attempting a second run while startup handlers are active.

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-a-starting-session-is-busy-during-before-agent-start-in-1-2

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Pi Coding Agent
    commit2026-10-13-pi-coding-agent-a-starting-session-is-busy-during-before-agent-start-in-1-2github.com/earendil-works/pi/commit/a447ba11f3e7760fcff91e924bda8c20033953eatagged commit file2026-10-13-pi-coding-agent-a-starting-session-is-busy-during-before-agent-start-in-1-2earendil-works/pi / packages/coding-agent/CHANGELOG.md

Versioned source: run artifact