Diskless cloud sessions refuse disk-dependent features and explain why

What

Some cloud sessions are launched with no disk to save files to (host.launchOptions.diskless()). Several features now check for this:

• Refreshing a claude.ai marketplace (a source of plugins) fails with "was not refreshed: this session can't save claude.ai marketplaces" (kind diskless), and removing one does nothing.
• Adding a claude.ai marketplace fails with "claude.ai marketplaces can't be added in this session, because it can't save them".
• Hooks modules ("mods", add-ons that change how Claude Code behaves) are not loaded, and the reasons list gains diskless: "this kind of cloud session has no disk to load mods from". It is wired as a refusal, { refusal: "diskless", isRefused: Ln }.
• Loading folders of markdown files uses the path that does not rely on ripgrep, a fast file-search program.
• The Read, Write and Glob tools no longer resolve paths against the current folder for tools that never run locally in this mode.
• After compaction (when Claude Code summarizes an earlier part of a long conversation to save space), the summary no longer tells the model to "read the full transcript at:" a path, and no longer notes that "the full transcript mentioned above still has it", when the session is diskless (!Ln()). Before, the sentence was added whenever a transcript path existed.

Why

In diskless sessions you get a stated reason instead of mods or marketplaces silently failing, and the model is no longer sent to read a transcript file that does not exist.