{"version":"2.1.234","anchor":"permission-mode-changes-are-announced-on-the-stream-json-out","canonical_anchor":"permission-mode-changes-are-announced-on-the-stream-json-out","heading":"Permission mode changes are announced on the stream-json output","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/permission-mode-changes-are-announced-on-the-stream-json-out","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Permission mode changes are announced on the stream-json output\n\nScripted sessions now get a stream-json status message whenever the permission mode changes.\n\n**What**\n\nProgrammatic sessions (SDK and `--output-format stream-json`) now get a message whenever the permission mode changes: `{type:\"system\", subtype:\"status\", status:null, permissionMode, uuid, session_id}`. The same status is re-sent when a remote client reconnects or attaches, so a client that joined late still knows the current mode. Controlled by `tengu_wobbly_pinwheel`, which falls back to true, so it is on unless remote config turns it off.\n\n**Details**\n\n- The emission on mode change sits behind a flag helper; the reconnect\/attach resend keeps late joiners in sync.\n- `status` is null on these messages; the mode itself is carried in `permissionMode`.\n\n**Evidence**\n\n`tengu_wobbly_pinwheel`\n\n- Flag `tengu_wobbly_pinwheel`: Not enough to say (read for one account on one subscription tier against v2.1.234; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: SDK\n- Names: `--output-format stream-json`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}