{"version":"2.1.300","anchor":"diskless-sessions-transcript-relocation-and-design-oauth-re","canonical_anchor":"diskless-sessions-transcript-relocation-and-design-oauth-re","heading":"Diskless sessions refuse to move transcripts and ask for a fresh design sign-in","tier":"notice","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/diskless-sessions-transcript-relocation-and-design-oauth-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Diskless sessions refuse to move transcripts and ask for a fresh design sign-in\n\nIn a diskless session, Claude Code refuses to move the transcript between project folders and asks for a new design sign-in instead of refreshing it\n\n**What**\n\nClaude Code now has guards for a \"diskless\" session, one whose transcript (the saved record of the conversation) is not kept in project folders on disk. In such a session:\n\n- moving the transcript from one project folder to another is refused, with the message \"A diskless session moves no transcript between project folders on disk\"\n\n- refreshing the sign-in for design features does not happen; Claude Code reports that a fresh design login is needed\n\n**Why**\n\nThese checks stop Claude Code from trying disk-based steps in a session that has nothing on disk to work with. In a diskless session, expect to sign in to design features again rather than having it renewed in the background.\n\n- Area: Diskless Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}