Remote permission approvals can name the tool they applied to, off in interactive sessions.
nameToolOnPermissionAllow is on for headless cloud clients, defaulted off elsewhere by tengu_violin_wood.
tengu_violin_wood Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.248: on
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new remote session option, nameToolOnPermissionAllow, makes an allow answer sent over the remote control channel include the name of the tool it applied to. The headless cloud client turns it on unconditionally; interactive remote sessions default it from tengu_violin_wood, which compiles in as false, so it is off there unless enabled server-side.
- The option is new in this build.
- Interactive sessions share the same default predicate used for keeping undelivered responses.
nameToolOnPermissionAllow
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.221
Session titles are normalised and blank titles rejected
Both mention name
-
v2.1.221
Background session names starting with "-" survive respawn
Both mention name
-
v2.1.223
Cloud sessions started with a title rename themselves instead of auto-titling
Both mention name