{"version":"2.1.268","anchor":"fork-seed-size-cap-and-stale-mtime-housekeeping","canonical_anchor":"fork-seed-size-cap-and-stale-mtime-housekeeping","heading":"Fork seed size cap and stale-mtime housekeeping","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/fork-seed-size-cap-and-stale-mtime-housekeeping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Fork seed size cap and stale-mtime housekeeping\n\nFork snapshot files get a hard size cap and a background-wait timer becomes configurable\n\n**What**\n\nThe snapshot files written when forking a conversation (see the new `fork_conversation` tool) now have a fixed maximum size, and writing one that exceeds it now fails with a dedicated error instead of succeeding silently. A separate internal helper keeps a snapshot file's modification time fresh, and a new environment variable, `CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS`, controls a related ceiling on how long a background wait can run.\n\n**Why**\n\nThe size cap prevents oversized conversation forks from being written unbounded, and the new environment variable gives more control over background-wait timing in headless or scripted use.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}