{"version":"2.1.311","anchor":"file-read-gains-an-empty-verdict-memory-type-tasks-and-no","canonical_anchor":"file-read-gains-an-empty-verdict-memory-type-tasks-and-no","heading":"Empty files read as empty, plus a new kind of background memory task","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/file-read-gains-an-empty-verdict-memory-type-tasks-and-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Empty files read as empty, plus a new kind of background memory task\n\nEmpty files are now read as empty text, and a new post-turn memory background task type and notice counter appear\n\n**Unclear.** It is not clear whether the new post-turn memory tasks are ever started or what they do.\n\n**What**\n\nSeveral small internal changes:\n\n- reading a file now decides between skipping it, treating it as empty, or reading it, and an empty file gives empty text\n\n- a new background task type for memory after a turn is recognised alongside the existing ones\n\n- each session now keeps count of which notices have been shown\n\n- the list of output files is now capped by a size limit\n\n**Why**\n\nMost of this is groundwork with little to see yet. Empty files are now handled as their own case when read.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}