{"version":"2.1.307","anchor":"agent-classifier-sends-a-beta-header-and-uses-global-cache-s","canonical_anchor":"agent-classifier-sends-a-beta-header-and-uses-global-cache-s","heading":"Auto mode's safety check can send an extra beta header","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/agent-classifier-sends-a-beta-header-and-uses-global-cache-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Auto mode's safety check can send an extra beta header\n\nThe check auto mode runs on actions now sends an extra beta header and uses a global cache scope when a certain condition holds\n\n**What**\n\nIn auto mode, Claude Code sends a separate request to a classifier, a check that decides whether an action may go ahead. When a certain condition holds, that request now uses a global cache scope and also sends an extra beta header, which asks the API for a feature that is still in testing. Before, no extra beta header was sent and the cache scope was chosen another way.\n\n**Why**\n\nThe requests behind auto mode's checks now carry different headers.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}