{"version":"2.1.290","anchor":"uds-messaging-is-skipped-in-restricted-sessions","canonical_anchor":"uds-messaging-is-skipped-in-restricted-sessions","heading":"Messaging between sessions does not start in restricted sessions","tier":"notice","area":"Messaging","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/uds-messaging-is-skipped-in-restricted-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Messaging between sessions does not start in restricted sessions\n\nMessaging between sessions no longer starts in a restricted session, or when an explicit messaging socket path is given\n\n**Unclear.** What makes a session count as restricted is not settled.\n\n**What**\n\nClaude Code can let separate sessions on the same machine send messages to each other through a local socket (a file-like connection point). This messaging now does not start up in two cases:\n\n- the session is a restricted session, in which case it logs `[uds-messaging] Skipped: restricted session`\n\n- `--messaging-socket-path` was given\n\n**Why**\n\nA restricted session cannot receive messages from other sessions.\n\n- Area: Messaging\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}