Disable Background Agents Fleet Setting / Claude Code v2.1.121

What

New disableAgentsFleet setting and CLAUDE_CODE_DISABLE_AGENTS_FLEET environment variable to fully disable the background-agents fleet.

Details

Evidence

Fleet disable option (search for "Disable the background-agents fleet", "CLAUDE_CODE_DISABLE_AGENTS_FLEET")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

The build it came inv2.1.121

27 Apr 2026 · 32 entries, this one is #8.

Either side of it

Open the release →

Names in this entry

envCLAUDE_CODE_DISABLE_AGENTS_FLEET
A true value (1, true, yes, on) turns off the background-agents fleet, the same as the disableBackgroundAgents setting: the fleet gate that otherwise follows tengu_slate_meadow returns false, so claude daemon subcommands that need the gate stop with 'daemon' is not enabled., the built-in Claude agent is left out of the built-in agent list, and claude daemon run exits with claude daemon: background agents disabled (ZDR/3P/opt-out).
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
slash/background
Detach the current session to run as a background agent and free this terminal. Pass a prompt to send one more instruction before detaching. Monitor the session with claude agents. To copy the conversation into a new background session while this one keeps running, use /fork. Alias: /bg

Is this right?