{"version":"2.1.232","anchor":"scratch-files-are-written-per-session-instead-of-one-shared-","canonical_anchor":"scratch-files-are-written-per-session-instead-of-one-shared-","heading":"Scratch files are written per session instead of one shared directory","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/scratch-files-are-written-per-session-instead-of-one-shared-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Scratch files are written per session instead of one shared directory\n\nScratch files now live in a per-session directory so concurrent sessions don't collide.\n\n**What**\n\nBackground task output links, project documentation copies and fetched project files now go into a directory derived from the current session rather than one global temp directory, so concurrent sessions do not share scratch space.\n\n**Details**\n\n- Affects files named `project-doc-*.txt` and `project-file-*` as well as task output.\n- The session directory is created on demand at write time.\n\n**Evidence**\n\n`project-doc-`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}