Scripted sessions now get a stream-json status message whenever the permission mode changes.
tengu_wobbly_pinwheel Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.234: off
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Programmatic 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.
- The emission on mode change sits behind a flag helper; the reconnect/attach resend keeps late joiners in sync.
statusis null on these messages; the mode itself is carried inpermissionMode.
tengu_wobbly_pinwheel
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
New
tool_host_resultsystem message in stream-json outputBoth mention output format stream json
-
v2.1.224
Compact summaries are flagged as synthetic in SDK output
Both mention output stream json
-
v2.1.229
Injected stream-json user messages no longer count as human turns
Both mention stream json