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

Finding / omp

2026-10-13-omp-broker-clients-stopped-letting-a-delayed-refresh-resurrect-logout-or-replace-a-newer-login

Broker clients stopped letting a delayed refresh resurrect logout or replace a newer login. A refresh reply used to overwrite newer local knowledge of broker credentials, potentially restoring a removed account to a client’s rotation or replacing a newer login. The client now refreshes its snapshot when its copy changed during the outstanding request and keeps current broker state.

Channel: tagged-release. Half: defect. Date: 2026-10-02 (v18.4.11).

Operator consequence: Upgrade the broker client, including gateways using that client, to v18.4.11 or later. This closes the inspected refresh-reply race; it is not proof that every delayed credential mutation is guarded.

Receipt

Finding metadata

Confidence
high

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

Finding ID: 2026-10-13-omp-broker-clients-stopped-letting-a-delayed-refresh-resurrect-logout-or-replace-a-newer-login

Source links

Primary links, including exact changelog lines when available.

  1. OMP (Oh My Pi)
    commit2026-10-13-omp-broker-clients-stopped-letting-a-delayed-refresh-resurrect-logout-or-replace-a-newer-logingithub.com/can1357/oh-my-pi/commit/9b54ded2389745ffd6ed36e892ceefc8512ab5e7tagged commit file2026-10-13-omp-broker-clients-stopped-letting-a-delayed-refresh-resurrect-logout-or-replace-a-newer-logincan1357/oh-my-pi / packages/ai/src/auth-broker/remote-store.ts