Workflow arguments sent as a JSON string are now parsed instead of failing.
tengu_jade_compass 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.229: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.229. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When the Workflow tool receives its args as a JSON-encoded string starting with { or [, it now parses it back into a real object or array rather than failing. The repair is controlled by the tengu_jade_compass flag, which falls back to on, so absent a server value the repair applies. With the flag off the same case is only recorded, and the original malformed input is passed through unchanged.
- The detected shape is classified as
args_json_string_to_objectorargs_json_string_to_array, each with a_namedvariant. - When the flag is off, a
_detect_onlysuffix is added to that classification.
args_json_string_to_object
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.239
Workflow tool gains run operations, with the auto-approval hook switched off
Both mention workflow
-
v2.1.239
Workflow tool has a second command shape built in but switched off
Both mention workflow
-
v2.1.239
Workflow "v2 run" handles are scaffolded but never created
Both mention workflow