Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Project and agent dispatch still need an endpoint your account may not have

You'll notice
Useful3 Signal3
Cloud Sessions not in their notes

Cloud sessions with --project or a specific agent are refused if your account lacks the newer endpoint.

--project
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →