Cloud sessions from review or plan sources can use a newer creation endpoint allowing --project grouping.
The newer endpoint and its --project and agent dispatch support need a server flag that falls back to off.
tengu_woven_harbor 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.224: not a boolean we can read
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.224. 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 a cloud session comes from an ultrareview or ultraplan source and the tengu_woven_harbor server flag is on, creation uses a newer endpoint, and only then are grouping sessions under a --project and dispatching to a Kindling agent accepted instead of refused. The flag falls back to off when the server sends no value, so by default the existing refusals still apply.
tengu_woven_harbor
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.227
Device-bound sessions reject
--projectand agent ownership up frontBoth mention project
-
v2.1.242
Owner messages in Claude Code Projects arrive as marked user turns
Both mention project
-
v2.1.242
Owner messages from MCP results can count as you speaking, currently dark
Both mention project