{"version":"2.1.232","anchor":"session-logs-get-a-place-in-the-managed-storage-layer","canonical_anchor":"session-logs-get-a-place-in-the-managed-storage-layer","heading":"Session logs get a place in the managed storage layer","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/session-logs-get-a-place-in-the-managed-storage-layer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Session logs get a place in the managed storage layer\n\nSession transcripts can be addressed through managed storage by project and date, and \/debug reads them that way.\n\n**What**\n\nSession transcripts can now be addressed through Claude Code's managed storage layer, keyed by project, date and log name, and `\/debug` reads its log that way when that storage layer is available.\n\n**Details**\n\n- The key is built from a project key, a year\/month\/day triple that is validated, and a log name that must match the session log's own name.\n- The scope is listable, so logs under a project and date can be enumerated.\n- Without the storage backend, `\/debug` falls back to reading the log file directly.\n\n**Evidence**\n\n`sessionLog`\n\n- Area: Sessions\n- Names: `\/debug`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}