{"version":"2.1.323","anchor":"new-data-flow-field-on-api-requests-with-a-fallback-when-th","canonical_anchor":"new-data-flow-field-on-api-requests-with-a-fallback-when-th","heading":"Requests can now carry a record of where data came from","tier":"soon","area":"Data Flow","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/new-data-flow-field-on-api-requests-with-a-fallback-when-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Requests can now carry a record of where data came from\n\nRequests to the API can carry a data_flow field about tool calls and data sources, dropped if the API refuses it\n\n**Unclear.** Exactly what information the data_flow field contains is not stated.\n\n**What**\n\nRequests 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.\n\n- 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.\n\n- When `ANTHROPIC_UNIX_SOCKET` is set, the field is never sent.\n\n**Why**\n\nThis 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.\n\n- Area: Data Flow\n- Names: `data_flow`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no\n- Present in the build but not switched on"}