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

Finding / flue

2026-10-13-flue-2-1-1-keeps-useflueagent-streaming-after-reload-while-an-observed-submission-remains-unset

2.1.1 keeps useFlueAgent streaming after reload while an observed submission remains unsettled. After a reload, useFlueAgent derives active submission ids from observed messages minus settlements. A running tool or silent admitted prompt that has appeared in the conversation now stays streaming rather than looking idle until assistant text arrives. A submission admitted but not yet materialized into a message at reload time remains a documented residual window.

Channel: tagged-release. Half: defect. Date: 2026-09-23 (2.1.1 publication; code committed 2026-09-22).

Operator consequence: Upgrade React chat clients from 2.1.0 to at least 2.1.1 so a reload does not invite a duplicate send merely because a tool is silent. Treat status as aggregate conversation activity, and preserve submission receipts if your UI must cover the residual pre-message window. The current 2.3.0 pin includes the fix.

Receipt

Finding metadata

Confidence
high

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

Finding ID: 2026-10-13-flue-2-1-1-keeps-useflueagent-streaming-after-reload-while-an-observed-submission-remains-unset

Source links

Primary links, including exact changelog lines when available.

  1. Flue
    commit2026-10-13-flue-2-1-1-keeps-useflueagent-streaming-after-reload-while-an-observed-submission-remains-unsetgithub.com/withastro/flue/commit/4685436f75fe0aea1fe661f47969d053742de221tagged commit file2026-10-13-flue-2-1-1-keeps-useflueagent-streaming-after-reload-while-an-observed-submission-remains-unsetwithastro/flue / CHANGELOG.md#L48-L49github release2026-10-13-flue-2-1-1-keeps-useflueagent-streaming-after-reload-while-an-observed-submission-remains-unsetwithastro/flue / %40flue%2Freact%402.1.1