--await-claim can no longer be combined with --sdk-url

--await-claim can no longer be combined with --sdk-url

Claude Code now refuses to start when --await-claim and --sdk-url are used together

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

3Signal: worth watching, 1 to 5

CLIArea: what it touches

ImprovementsKind: in v2.1.304, 19 Oct 26

ImprovementsSection of the release

What

A flag is an option you add to the claude command when you start it. Claude Code now stops at startup with the error "--await-claim cannot be used with --sdk-url." when both flags are given.

This joins the existing cases where --await-claim is refused:

--sdk-url, which is the new one
--continue, --resume or --fork-session
the CLAUDE_CODE_SUBPROCESS_ENV_SCRUB environment variable

Why

Any script that starts Claude Code with both --await-claim and --sdk-url will now fail immediately and needs one of the two flags removed.

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed claude --help text for --tools, --resume, --debug, --json-schema, --disable-slash-commands, --system-prompt-snapshot and claude update…

See this entry in the whole of v2.1.304 →

The build it came inv2.1.304

19 Oct 2026 · 371 entries, this one is #81.

Use it now20
You'll notice186
Nothing to try yet7
Under the hood158

Either side of it

v2.1.303Older
v2.1.305Newer

Open the release →

Names in this entry

cli--sdk-url
Startup stats now note the input format, whether --sdk-url was passed, and an experiment flag.
cli--continue
Load the most recent conversation in the current directory, including a background session that has finished; opening finished background sessions requires Claude Code v2.1.257 or later. Skips sessions created with claude -p or the Agent SDK, and sessions whose first prompt was /loop. claude -p --continue includes -p, SDK, and /loop sessions. Includes sessions that added this directory with /add-dir
cli--resume
Resume a specific session by ID or name, or show an interactive picker to choose a session. In place of an ID, you can pass the absolute path to a session's .jsonl transcript file. The picker and name search include sessions that added this directory with /add-dir. When you pass a session ID, Claude Code searches the current project directory and its git worktrees, then every other project on this machine. Before v2.1.223, the ID search covered only the current project directory and its git worktrees. Background sessions appear in the picker marked with bg
cli--fork-session
When resuming, create a new session ID instead of reusing the original (use with --resume or --continue)
envCLAUDE_CODE_SUBPROCESS_ENV_SCRUB
A hidden --inherit-permission-mode flag lets a spawned session take its permission mode from whatever launched it.

Anthropic's note

Upstream's own release notes for v2.1.304 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed claude --help text for --tools, --resume, --debug, --json-schema, --disable-slash-commands, --system-prompt-snapshot and claude update to match actual behavior

Is this right?

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