{"version":"2.1.318","anchor":"permission-request-envelope-gets-conversation-idcompaction","canonical_anchor":"permission-request-envelope-gets-conversation-idcompaction","heading":"Permission requests from cloud sessions can carry conversation and compaction IDs","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/permission-request-envelope-gets-conversation-idcompaction","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Permission requests from cloud sessions can carry conversation and compaction IDs\n\nPermission requests can now include a conversation ID and a compaction ID, and Claude Code can read such requests coming from a cloud session\n\n**Unclear.** It is not clear whether reading permission requests from cloud sessions is switched on for anyone yet.\n\n**What**\n\nA permission request is the message Claude Code sends when it needs your approval before using a tool. These requests now accept two extra pieces of information:\n\n- `conversation_id`, which identifies the conversation.\n\n- `compaction_id`, which identifies a compaction, the step where Claude Code summarizes a long conversation to free up space.\n\nClaude Code can also now read permission requests that arrive from a session running in the cloud. It limits how large such a request can be and gives a reason when it refuses one.\n\n**Why**\n\nThis is part of the system that lets tools run on a remote host while you approve them from Claude Code.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}