{"version":"2.1.293","anchor":"fetch-wrapper-uses-abortsignalany-to-combine-abort-signals","canonical_anchor":"fetch-wrapper-uses-abortsignalany-to-combine-abort-signals","heading":"Network requests with a time limit handle cancelling more cleanly","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/fetch-wrapper-uses-abortsignalany-to-combine-abort-signals","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Network requests with a time limit handle cancelling more cleanly\n\nRequests with a time limit now combine your cancel and the timeout into one signal, instead of forwarding the cancel by hand\n\n**What**\n\nWhen Claude Code makes a network request with a time limit, it now joins your cancel and its own timeout into one signal using `AbortSignal.any`. Before, it forwarded your cancel through a separately attached listener.\n\n**Why**\n\nThis avoids leaving that listener behind and makes cancelling behave more cleanly. There is little visible effect.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}