{"version":"2.1.300","anchor":"hosted-sessions-oauth-refresh-refused-diskless-memory-dir","canonical_anchor":"hosted-sessions-oauth-refresh-refused-diskless-memory-dir","heading":"Hosted server sessions without a disk no longer refresh login tokens","tier":"internal","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hosted-sessions-oauth-refresh-refused-diskless-memory-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hosted server sessions without a disk no longer refresh login tokens\n\nIn hosted claude-code-server sessions, Claude Code now refuses to refresh OAuth login tokens and skips creating its memory folder\n\n**What**\n\nSome Claude Code sessions run on a hosted server, called claude-code-server, that has no disk to save files to. In these sessions, two things now behave differently:\n\n- OAuth token refresh: An OAuth token is the login credential Claude Code uses to talk to your account, and it is renewed from time to time. A hosted session without a disk now refuses to renew it and reports that it cannot refresh an OAuth token.\n\n- Memory folder: Claude Code no longer tries to create the folder where it keeps memory files.\n\nSeparately, the lock that prevents two token renewals at the same time is now kept per login slot instead of as one shared lock.\n\n**Why**\n\nThese changes point to a hosted mode in which Claude Code runs with no disk at all. In that mode it no longer attempts steps that need to save files.\n\n- Area: Diskless Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}