Cloud session creation can use a newer request shape for review and plan sources.
The newer create body applies only when an account check passes, and nothing in this build sets it.
What's wrong with this entry?
Creating a cloud session can now build a different request body for the newer session-create endpoint, carrying worker, source, outcome, seed bundle and branch-reuse fields in place of the older single session-context blob. It applies only when an account-level check passes and the session comes from ultrareview or ultraplan; nothing in this build sets that check, so what accounts get is decided elsewhere. --project and agent dispatch still refuse outright on accounts still using the old endpoint.
v1alpha2
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