Signals

2026-10-24 / Paperclip

Paperclip brings Operator grants and durable accounting to stable

Edited by Michael Ruescher

Stable v2026.1023.0, published on GitHub on 2026-10-24, delivers former-beta changes. Existing active human Operators can receive fourteen default grants through compatibility seeding. Usage receipts now survive until committed settlement, with idempotent accounting and serialized admission. Unpriced usage blocks only under the applicable active, positive-amount hard-stop policy, not as an unconditional ceiling on the provider bill.

What this changes for operators

  • Instance administrators: drain old writers and preserve SQLite lock files before upgrading to v2026.1023.0. Inspect human roles and persisted scopes before restart and sign-in; use a narrower role or a verified restrictive stored scope where configuration rights are unwanted, since missing grant rows can be reinserted. Existing scoped rows survive conflict handling.
  • Finance and platform owners: retain unsettled receipts, choose the unpriced-usage policy explicitly and reconcile an interrupted/retried run against provider evidence. Persisted-grant comparisons and billed settlement traces would close acceptance; released code alone closes only delivery. Durable records can replace manual cost reconstruction.
  • Inventory workers separately: stable’s remote Codex range is >=0.149.0 and <0.161.0, so standalone Codex 0.164.0 is outside it. Keep the native call_api parity repair and later review/Stop fixes in their preview lane. A stable platform upgrade does not qualify those workers or fixes.

Primary sources

Signal metadata

Source findings

Featured in

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-10-24-paperclip-stable-grants-and-accounting-migration

Research evidence and publication history are open in the repository.