Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

Workflow run IDs get a dedicated format and telemetry hashing path

Workflow run IDs now use a dedicated ID format with their own telemetry hashing path

Under the hood Internal Changes
JSON All of v2.1.265
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WorkflowsArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
What

Workflow run IDs now follow a specific recognizable shape (a wf_ prefix followed by hex characters). Internally, IDs matching this shape are now hashed and redacted differently from other custom identifiers before being included in telemetry data.

Why

This is an internal bookkeeping change affecting how workflow run identifiers are anonymized before being sent in telemetry; it doesn't change what you see or do when using workflows.

Read from
Names in the bundlewf_
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up wf_, on Monitoring. | `workflow.run_id` | Run identifier of the [Workflow](/docs/en/workflows) tool run that spawned this agent, prefixed `wf_`. Absent for agents not spawned by a workflow | | monitoring-usage see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up wf_, on Monitoring.

See this entry in the whole of v2.1.265 →

Feedback