{"version":"2.1.307","anchor":"projects-thread-standing-ask-carry-across-compaction-and-a","canonical_anchor":"projects-thread-standing-ask-carry-across-compaction-and-a","heading":"A pending request in a Project thread can now survive compaction","tier":"notice","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/projects-thread-standing-ask-carry-across-compaction-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### A pending request in a Project thread can now survive compaction\n\nA standing request in a Project thread can now be carried across compaction, and the auto mode check handles more message patterns around replies\n\n**Unclear.** It is not clear which accounts have Project threads or what switches this behaviour on.\n\n**What**\n\nCompaction is when Claude Code summarises the older part of a long conversation to free up space. In a Project thread, a request that is still waiting for an answer can now be carried across compaction when the kept part of the conversation is its most recent end. It is not carried if the request was already answered or was edited.\n\nAuto mode is where a check decides whether Claude may go ahead without asking you. Its instructions for Project threads have a version that tolerates:\n\n- notices that notifications are queued\n\n- messages from the same person sent just before a reply\n\nReplies that match a request are now marked as coming from a person.\n\n**Why**\n\nThis affects whether a short reply such as 'ok' in a Project thread is still taken as your answer after the conversation has been compacted.\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}