{"version":"2.1.302","anchor":"http-client-hooks-beforerequest-credentialrequestheaders","canonical_anchor":"http-client-hooks-beforerequest-credentialrequestheaders","heading":"Claude Code's web request setup accepts three more options","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/http-client-hooks-beforerequest-credentialrequestheaders","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Claude Code's web request setup accepts three more options\n\nClaude Code's own web request setup can now run steps before a request, mark credential headers and decide when to resend\n\n**What**\n\nClaude Code has an internal setup step that controls how its own web requests are made. Before, it accepted only a step that runs on each response and a set of extra request headers. It now also accepts:\n\n- steps that run before each request is sent\n\n- a list of header names that carry credentials, meaning login details such as tokens\n\n- rules that decide whether a request should be sent again\n\n**Why**\n\nThis lays groundwork for resending a request when its login details need attention. Nothing visible changes yet from this alone.\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"}