What
Creating a cloud session with --project, a session group, or a specific agent id requires the newer session-create endpoint. If your account is on the older one, creation is refused outright with a message naming the reason, project_not_enabled or agent_not_enabled, and no session is started.
Details
- The newer endpoint is chosen when no environment variables were passed and an async check passes, or when the request came from ultrareview or ultraplan and a separate gate passes; otherwise the older endpoint.
- The ultrareview/ultraplan branch is decided remotely; what it falls back to is not visible in this build.
Evidence
Dispatching into a Kindling project requires the new session-create endpoint, which isn't enabled for your account yet — no session was created.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle--project
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up --project, on cmek-google-cloud-kms.
* **Domain restricted sharing:** the `constraints/iam.allowedPolicyMemberDomains` org policy can strip the Anthropic service account binding (see the earlier note). Confirm the binding is present with `gcloud kms keys get-iam-policy <your-…manage-claude/cmek-google-cloud-kms see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --project, on cmek-google-cloud-kms.