Bitter Frontier What agents made cheaper, where the bottleneck moved, and what deserves attention.

Signals / Flue profile

Flue

Sourced signals for Flue: release changes, governance moves, runtime shifts, and operator consequences. Each links to the run that produced it. The Flue profile carries the current evergreen state.

June 2026

  1. 2026-06-23 / Flue

    Flue workflow runs go private by default and flue logs is removed (staged in Unreleased)

    Runtime
    • Staged in the CHANGELOG `## Unreleased` section on main (NOT in the in-window v1.0.0-beta.1/beta.2 tags): workflow runs become private over HTTP unless the workflow separately exports a `runs: WorkflowRunsHandler`, admission receipts shrink to `{ runId }`, `streamUrl`/`offset` are dropped, and the `flue logs` command is removed in favor of typed SDK access (`client.runs.get()`/`events()`/`stream()`).
    • This is direction, not a shipped default: the in-window beta.1 tag still documents `flue logs` as functional with the old `{ streamUrl, offset }` envelope. Operators should plan migrations off `flue logs` and the old run envelope, but not assume the new default is live until it tags.

    Run: 2026-06-23-weekly-digest-2026-06-16_2026-06-23-frontier-v0

  2. 2026-06-08 / Flue

    Flue reaches a 1.0-line beta and makes durable, recoverable agent execution the default

    Runtime
    • Flue shipped durable, recoverable agent execution with pluggable SQLite or Postgres persistence (0.10.0) and reached its first 1.0-line beta (1.0.0-beta.1), a migration-heavy stabilization (valibot tool schemas, opaque run_<ulid> IDs, run-introspection exports). It also swapped standard WebSocket and SSE for a proprietary Durable Streams transport (0.10.2), narrowing external observability. Category evidence that the model+harness split is maturing into stateful infrastructure; the experimental-API caution starts to lift.

    Run: 2026-06-16-weekly-digest-2026-06-04_2026-06-16-frontier-v0

  3. 2026-06-03 / Flue

    v0.9.0 breaking app-config migration: routing/provider imports, provider-ID format, SDK mount paths, and beta session-state reset

    Platform
    • Upgrading to v0.9.0 forces a developer to rewrite application imports: routing moves from `@flue/runtime/app` to `@flue/runtime/routing`, provider APIs and `observe` come from `@flue/runtime`, and Workers AI types from `@flue/runtime/cloudflare` — code will not compile until updated.
    • Provider model values now require `provider-id/model-id` format and `registerProvider()`/`configureProvider()` must share one ID; SDK mount paths now derive from `baseUrl` pathname — both are silent runtime-behavior changes that mis-route calls if not updated.
    • Persisted beta session state is now rejected; the operator must clear or migrate the session store before upgrading or sessions fail to restore — a distinct destructive pre-upgrade step gated on the same v0.9.0 cutover.
    • All of these share one verb (update-before-upgrade) for one persona (the Flue app developer) and one verification path (build + smoke-test against v0.9.0), so they route as a single platform migration signal.

    Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0

  4. 2026-06-03 / Flue

    v0.9.1 strips WebSocket URL credentials and rejects blank requestIds

    Runtime
    • Operators deploying Flue on Cloudflare WebSockets get two upstream hardening fixes by upgrading to v0.9.1: query strings and fragments are stripped before attachment persistence, so URL-carried handshake credentials are no longer retained, and agent/workflow frames reject blank or whitespace-only `requestId` values.
    • Both are the same consequence for one persona (the Cloudflare WebSocket operator) gated on the same upgrade, so they stay one signal; the operator action is to upgrade and confirm credentials are no longer in persisted attachments.

    Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0

  5. 2026-06-03 / Flue

    v0.9.2 adds an activate_skill tool letting agents load skills autonomously

    Control Plane
    • Operators configuring skills now get a new agent-facing `activate_skill` tool: agents load full skill instructions on demand before matching work, shifting skill loading from operator-orchestrated to agent-initiated — a proactivity/authority change the operator should be aware of when scoping which skills are available.
    • Workspace skills are reread on activation, so edits during an active session take effect (lazy loading preserved); verification is concrete (configure a skill, confirm the agent self-activates it and picks up an edit mid-session).

    Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0

May 2026

  1. 2026-05-12 / Flue

    Flue: programmable harness with run observability, virtual sandbox, and shell env security fix

    Platform
    • Operators using shell env for credentials in pre-v0.4.1 Flue sessions should verify their session store does not contain unredacted values — the v0.4.1 shell env redaction fix is a security patch.
    • Operators using `sandbox: 'local'` should re-test: it is now genuinely local (direct host access, no just-bash), changing the isolation boundary for agents running in CI.
    • Operators building on Flue should evaluate `flue logs` and run history (v0.5.0) as the primary evidence trail for autonomous agent invocations.

    Run: 2026-05-12-partial-cycle-flue-2026-05-07_2026-05-12-frontier-v0

<- All signals