150 wires and counting

$ follow Anthropic

Keep up with Anthropic in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-07-12
stories 45

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

CYBER RUNBOOK TRAFFIC NOW TRACEABLE IN TELEMETRY

By RepoJournal · Filed · About Anthropic · Composed from the cited sources · methodology

Pipeline agents and interactive sessions in defending-code now send attributable usage markers so runbook traffic is visible across your request logs.

The defending-code reference harness shipped a critical instrumentation change that makes agent traffic identifiable in Anthropic's telemetry pipeline [1]. Outbound API requests from pipeline agents now carry an `anthropic-cyber-runbook: pipeline` header plus a `cyber-runbook/<version>` User-Agent token, while interactive skill sessions get a header-only marker via `.claude/settings.json` [2]. The header was renamed to the `anthropic-*` convention before shipping to ensure gateway allowlists would honor it on passthrough [3]. This is infrastructure work that enables observability without breaking anything, but it matters if you're monitoring where your agent traffic goes. On the plugin side, both official and community plugin repos are cycling through routine dependency bumps across hyperframes, twilio-developer-kit, carta-investors, and a half-dozen others [4][5][6][7][8][9][10][11][12][13][14][15]. All bumps are pre-validated via `claude plugin validate` before the PR lands. Nothing is broken, nothing is urgent, but the backlog is moving.

Action items

References

  1. [1] Add declared usage marker to agent API requests ↗ anthropics/defending-code-reference-harness
  2. [2] Add a declared usage marker to outbound agent API requests ↗ anthropics/defending-code-reference-harness
  3. [3] Rename usage-marker header to anthropic-cyber-runbook ↗ anthropics/defending-code-reference-harness
  4. [4] bump(hyperframes): 8c21736a → f53a75bf ↗ anthropics/claude-plugins-official
  5. [5] bump(hyperframes): 2aadf450 → 8c21736a ↗ anthropics/claude-plugins-official
  6. [6] bump(twilio-developer-kit): aa67a6d4 → 29f355c5 ↗ anthropics/claude-plugins-official
  7. [7] bump(carta-investors): 193e1a48 → a8b2c4bb ↗ anthropics/claude-plugins-official
  8. [8] bump(42crunch-api-security-testing): adf0b87c → 30287f5e ↗ anthropics/claude-plugins-community
  9. [9] bump(agent-estimate): 022b5298 → 8d84869c ↗ anthropics/claude-plugins-community
  10. [10] bump(agentforce-adlc): f17012bd → f7630726 ↗ anthropics/claude-plugins-community
  11. [11] bump(alloydb-omni): d45c1bd6 → 66a26476 ↗ anthropics/claude-plugins-community
  12. [12] bump(aomi-build): 1beccf94 → 74b90bc7 ↗ anthropics/claude-plugins-community
  13. [13] bump(twilio-developer-kit): aa67a6d4 → 29f355c5 ↗ anthropics/knowledge-work-plugins
  14. [14] bump(carta-investors): 193e1a48 → a8b2c4bb ↗ anthropics/knowledge-work-plugins
  15. [15] bump(pixeltable): 933c15b5 → ec4c931a ↗ anthropics/knowledge-work-plugins

Quick answers

What shipped in Anthropic on July 12, 2026?
Pipeline agents and interactive sessions in defending-code now send attributable usage markers so runbook traffic is visible across your request logs. In total, 3 commits and 42 pull requests landed.
Who contributed to Anthropic on July 12, 2026?
2 developers shipped this update, including eugeneyan-ant and github-actions.
What were the notable Anthropic updates?
Add declared usage marker to agent API requests, Add a declared usage marker to outbound agent API requests, and Rename usage-marker header to anthropic-cyber-runbook.