Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.323entry #32

Claude Code v2.1.323 ·

Requests can now carry a record of where data came from

Requests to the API can carry a data_flow field about tool calls and data sources, dropped if the API refuses it

Nothing to try yet No documentation found In Development
JSON All of v2.1.323
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Data FlowArea: what it touches
In DevelopmentKind: in v2.1.323,
What probably matters to youSection of the release

Unclear Exactly what information the data_flow field contains is not stated.

What

Requests that Claude Code sends to the API can now include a data_flow field. It is built from records of tool calls (actions Claude took), where data came from, and what was touched. The field is off unless it is switched on remotely, and it also depends on how you are signed in.

  • If the API rejects a request because of this field (an HTTP 400 error mentioning data_flow), Claude Code stops sending it for the rest of the session and sends the request again.
  • When ANTHROPIC_UNIX_SOCKET is set, the field is never sent.
Why

This adds information about where data came from to outgoing requests. That matters for privacy, and for anyone who runs a proxy, a server that sits between Claude Code and the API, since the proxy may see or reject the new field.

Read from
Names in the bundledata_flow
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtExactly what information the data_flow field contains is not stated.

See this entry in the whole of v2.1.323 →

Feedback