Paperclip
Paperclip adds ACP usage and cost data to spend telemetry
Paperclip is carrying ACP-lane token usage and cost into its spend records, closing an accounting gap for operators tracking what workplace agents consume across adapter boundaries.
paperclipai/paperclip PR #9471 is the primary source for today’s Paperclip item: “fix(adapters): propagate ACP-lane usage and cost into spend telemetry.” ClawCharts placed Paperclip on the assignment desk at rank #3, but the public claim comes from the inspected source cluster, not the medal.
The facts: current baseline resolves to paperclipai/paperclip; the observed row showed None seven-day stars, unknown active contributors, unknown commits, and 73456 total stars; GitHub reports 73456 stars, 5004 open issues, default branch master, pushed_at 2026-07-13T00:28:45Z; release baseline is v2026.707.0 (2026-07-07T14:49:05Z).
What changed: fix(adapters): propagate ACP-lane usage and cost into spend telemetry. The source is current to 2026-07-13T00:35:22Z. Related/context links inspected for the cluster: paperclipai/paperclip PR #9470 — fix(heartbeat): throttle redundant issue re-wakes; paperclipai/paperclip PR #9469 — fix(adapters): inject execution contract once per fresh heartbeat; paperclipai/paperclip PR #9468 — perf(ui): improve Decisions scrolling performance; paperclipai/paperclip PR #8711 — [codex] Surface pending interactions in heartbeat context.
Why it matters: this is current project motion, the sort of plumbing that determines whether agent infrastructure is observable, governable, and recoverable under operator load.
Current: repo/product baseline, releases, PRs, issues, and community/discovery search surfaces were checked. Weak community hits, duplicate package mirrors, ambiguous name collisions, and stale keyword-only matches were rejected rather than promoted.
Caveat: GitHub-source items can describe work in motion rather than shipped product behavior, so this is filed as source-inspected operator news, not a release claim.
Operator context: the primary artifact is paperclipai/paperclip PR #9471, titled “fix(adapters): propagate ACP-lane usage and cost into spend telemetry.” It was selected after comparing the current repo, release baseline, recently updated pull requests and issues, and the public discovery surfaces used for this edition. The claim is deliberately narrow: the source shows current project motion or, for a quiet watchlist, the absence of a stronger fresh public event. It does not turn an unmerged proposal into shipped behavior, and it does not treat the ClawCharts position as evidence for the underlying claim.
Source cluster: paperclipai/paperclip PR #9470: fix(heartbeat): throttle redundant issue re-wakes; paperclipai/paperclip PR #9469: fix(adapters): inject execution contract once per fresh heartbeat; paperclipai/paperclip PR #9468: perf(ui): improve Decisions scrolling performance; paperclipai/paperclip PR #8711: [codex] Surface pending interactions in heartbeat context. These links are grouped because they show the adjacent operator surface around Paperclip, not because every item is equally important. The primary source carries the headline; supporting links provide comparison, implementation context, or evidence that the selected angle is not an isolated keyword hit. Package mirrors and generic search residue were excluded.
Operational reading: for teams evaluating Paperclip, the useful question is whether this work changes a trust boundary, control surface, integration seam, or maintenance burden. The current evidence is enough for a watch-or-test decision, not for an unconditional rollout recommendation. Operators should inspect merge or closure state, confirm the behavior against the version they run, and keep the caveat attached until the project’s own shipped baseline catches up. That boundary is dull but useful; infrastructure tends to punish decorative certainty.
Source-inspected operator brief; ClawCharts is assignment context, not claim evidence.