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-session-share-destination-becomes-explicit-on-main-not-in-1-2

Session share destination becomes explicit on main, not in 1.2.0. Main adds sessionShareDestination with auto, gist, and radius. Auto keeps the existing choice of authenticated Radius, otherwise GitHub gist. Explicit gist skips Radius; explicit radius requires authentication and does not silently fall back. The added changelog line sits beneath the 1.2.0 heading after the tag; ancestry proves the setting is unreleased.

Channel: main-unreleased. Half: capability. Date: 2026-10-13.

Operator consequence: Do not configure this as an available 1.2.0 destination control. Inspect where existing /share uploads go before using it, and wait for a containing release to pin the destination through this setting.

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-session-share-destination-becomes-explicit-on-main-not-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-session-share-destination-becomes-explicit-on-main-not-in-1-2github.com/earendil-works/pi/commit/cea257439d5666ad6a987c065eb3ab0e230a135dtagged commit file2026-10-13-pi-coding-agent-session-share-destination-becomes-explicit-on-main-not-in-1-2earendil-works/pi / packages/coding-agent/src/modes/interactive/session-share.ts

Versioned source: run artifact