{"version":"2.1.323","anchor":"side-queries-get-a-forced-no-tool-choice-and-a-data-flow-ret","canonical_anchor":"side-queries-get-a-forced-no-tool-choice-and-a-data-flow-ret","heading":"Side requests can choose their tool setting and retry without a rejected field","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/side-queries-get-a-forced-no-tool-choice-and-a-data-flow-ret","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Side requests can choose their tool setting and retry without a rejected field\n\nSide requests now pick their tool setting by purpose, and send a data_flow field that is dropped and retried if the API rejects it\n\n**What**\n\nBesides your main conversation, Claude Code sends smaller side requests to the model for its own jobs. Two things changed in these requests:\n\n- The tool setting, which says whether the model may use tools, can now be overridden based on what the request is for.\n\n- A data_flow field is now attached. If the API rejects the request because of it, Claude Code removes the field and sends the request again.\n\n**Why**\n\nThis changes the shape of the requests Claude Code sends to the API.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}