{"version":"2.1.236","anchor":"sandbox-managed-settings-and-plugin-prompts-now-use-the-shar","canonical_anchor":"sandbox-managed-settings-and-plugin-prompts-now-use-the-shar","heading":"Sandbox, managed-settings and plugin prompts now use the shared dialog channel","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/sandbox-managed-settings-and-plugin-prompts-now-use-the-shar","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Sandbox, managed-settings and plugin prompts now use the shared dialog channel\n\nSandbox, managed-settings and plugin prompts now go through one shared dialog system.\n\n**What**\n\nFour prompts move out of hand-rolled REPL state into the shared dialog registry: sandbox network host approval showing host and port, managed-settings security accept or reject, a plugin installation status notice, and a permission-mode accept or decline. Everyone on this build gets the new routing; there is no flag.\n\n**Details**\n\n- The removed inline code passed sandbox-host and managed-settings state to the status line and tracked their queues by hand.\n- Notification labels now show \"sandbox request\" for the sandbox prompt; the other three show \"dialog open\".\n- Those four kinds are excluded from the check that decides whether an open dialog blocks typing in the input area.\n\n**Evidence**\n\n`\"sandbox request\"`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}