New --managed-settings-in-initialize flag, not allowed with…

New --managed-settings-in-initialize flag, not allowed with background modes

Claude Code has a new --managed-settings-in-initialize flag, which refuses to run alongside --bg, --background, --routine or --tmux

Use it now Notable New Features

JSON All of v2.1.323

Use it nowTier: how much it should matter to you

5Useful: my rating, 1 to 5

3Signal: worth watching, 1 to 5

Managed SettingsArea: what it touches

New FeaturesKind: in v2.1.323, 12 Nov 26

What probably matters to youSection of the release

What

A flag is an option you add when starting a command. Claude Code has a new one, --managed-settings-in-initialize. It cannot be used together with any of these, and Claude Code stops with an error if you try:

--bg or --background
--routine
--tmux
a background session command

There is also a new faster route for claude plugin validate --module.

Why

It gives programs that build on Claude Code through the SDK a way to supply managed settings (settings an organization sets centrally) when the session starts, rather than from files on disk.

How sure we are

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

Anthropic's release notes agreeAdded type checking of a plugin's TypeScript hooks module to claude plugin validate; each finding is a warning, and --strict fails on it

See this entry in the whole of v2.1.323 →

The build it came inv2.1.323

12 Nov 2026 · 888 entries, this one is #24.

Use it now77
You'll notice533
Nothing to try yet64
Under the hood214

Either side of it

v2.1.322Older

Open the release →

Names in this entry

cli--bg
Start the session as a background agent and return immediately. Prints the session ID and management commands. Combine with --exec to run a shell command as a background job instead of a Claude session, or with --agent to run a specific subagent. Checks workspace trust for the directory before it starts. Can't be combined with -p/--print; see the error reference
cli--background
Start the session as a background agent and return immediately. Prints the session ID and management commands. Combine with --exec to run a shell command as a background job instead of a Claude session, or with --agent to run a specific subagent. Checks workspace trust for the directory before it starts. Can't be combined with -p/--print; see the error reference
cli--tmux
Create a tmux session for the worktree. Requires --worktree. Uses iTerm2 native panes when available; pass --tmux=classic for traditional tmux

Anthropic's notes

Upstream's own release notes for v2.1.323 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.

Added type checking of a plugin's TypeScript hooks module to claude plugin validate; each finding is a warning, and --strict fails on it
Added to claude plugin validate the $ nouns a mod's engine.create hook adds, withholds or replaces
Fixed claude plugin commands and claude mcp list signing you out of a Console profile when they ended while the token was being renewed
Fixed a session on a named Anthropic profile moving to another sign-in when /fork, the Left arrow or --bg continued it in the background; reopen any session that was open during the update
Changed claude plugin validate to fail a mod whose engine.create hook isn't written in the one accepted form; installed mods keep loading
Deprecated a plugin's agent setting: it still applies, and now warns at startup, in claude plugin list and in claude plugin validate

Is this right?