{"version":"2.1.271","anchor":"auto-mode-permission-classifier-context-can-now-shed-artifa","canonical_anchor":"auto-mode-permission-classifier-context-can-now-shed-artifa","heading":"Auto-mode permission classifier context can now shed 'artifacts' before erroring","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/auto-mode-permission-classifier-context-can-now-shed-artifa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Auto-mode permission classifier context can now shed 'artifacts' before erroring\n\nAuto mode's permission classifier can now drop 'artifacts' from its context before it errors on being too large\n\n**Unclear.** Whether the `tengu_auto_mode_context_static_over_budget` gate affects this behavior is unread for this site's account, so nothing can be said about it.\n\n**What**\n\nClaude Code's server-side auto-mode permission classifier builds a context payload that can include git state, prior-turn context, Chrome tabs, and now also `artifacts`. When that payload is too large, the classifier already had a system to shed less-important fields one at a time; it can now also shed `artifacts` before finally warning and giving up, at which point every one of these variable parts is left out of the request entirely.\n\n**Why**\n\nAdding `artifacts` as a shed-able field means a request that would otherwise fail for being oversized can still go through, with artifact state trimmed out first rather than the whole classifier context being dropped immediately.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}