{"version":"2.1.269","anchor":"new-get-memory-dialog-remote-request-subtype","canonical_anchor":"new-get-memory-dialog-remote-request-subtype","heading":"New get_memory_dialog remote request subtype","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-get-memory-dialog-remote-request-subtype","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New `get_memory_dialog` remote request subtype\n\nA new remote-control request type fetches memory-dialog data, but is blocked over headless connections\n\n**Unclear.** The finding doesn't explain what a 'memory dialog' or a 'dream' task is or does.\n\n**What**\n\nClaude Code's remote-control message handler (used by the SDK and by remote sessions) now supports a new request type, `get_memory_dialog`, which loads a helper to build and return data for a memory dialog, including whether a 'dream' task is currently running. This request is explicitly refused when made over a headless or remote connection.\n\n**Why**\n\nThis lets a client ask for memory-dialog information through the same remote-control channel used for other requests, while keeping it unavailable in contexts where showing a dialog wouldn't make sense.\n\n- Area: Remote Control\n- Names: `get_memory_dialog`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}