{"version":"2.1.317","anchor":"auto-mode-classifier-prompt-for-projects-threads-adds-backgr","canonical_anchor":"auto-mode-classifier-prompt-for-projects-threads-adds-backgr","heading":"Auto mode in Projects threads treats background reports differently","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/auto-mode-classifier-prompt-for-projects-threads-adds-backgr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Auto mode in Projects threads treats background reports differently\n\nIn Projects threads, reports from a session's own background work no longer affect how a bare reply is judged, and approve nothing\n\n**What**\n\nIn auto mode, Claude Code checks on its own whether you have approved an action. In Projects threads it looks at whether your last message answered Claude's last reply. When a new option is set, the instructions for that check now say:\n\n- Reports of the session's own background work, such as a background task's notice or a subagent's report, do not break that check.\n\n- Those reports approve nothing.\n\n- Notes sent to other sessions with `message_coordinator` or `message_thread` count like an edit, so a short reply after one is treated as unclear.\n\nBefore, only queued notices and messages from the same person were covered.\n\n**Why**\n\nThis changes when a short \"yes\" in a Projects thread counts as approval.\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"}