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

Signals

2026-09-21 / Eve

Queued messages from different users ran under the last sender's authorization

Edited by Michael Ruescher

Control Plane

PR 3172 (merge 3bbf8e5c, in eve@0.52.5 and not 0.52.4) groups queued deliveries by auth context; before it, messages from different users queued behind a running turn ran as one turn under the last sender's authorization. The previous issue told operators to set turnPolicy queue. PR 3203 (same release) stopped /eve/v1/info serializing the owner's BYOK provider API key to any caller the channel admits. eve@0.59.1 adds auto(), a model that approves tool calls and falls back to a human if review fails.

What this changes for operators

  • If you set turnPolicy queue on a multi-user channel, run eve@0.52.5 or later; before it, one user’s message could run with another’s authority.
  • Rotate any BYOK provider key served by an eve deployment older than 0.52.5.
  • Evidence that would settle residual: the first version that exposed the BYOK key, which the release notes do not state.

Primary sources

Signal metadata

Confidence
high

Source findings

Featured in

Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-09-21-eve-queued-messages-ran-under-the-last-sender

Research evidence and publication history are open in the repository.