/ Claude Code v2.1.166

--bg conflict error now correctly says --cloud instead of --remote: "Use claude --cloud '<task>' directly to start a cloud session." (search for "--bg and --cloud are different backends")

Policy limits cache telemetry at first prompt now additionally reports cache_age_ms and would_fail_closed, giving Anthropic better visibility into whether rate-limit enforcement would have failed due to a stale cache. (search for "would_fail_closed")

Shell allow-rule telemetry is now fired at initialization (tengu_shell_allow_rules_at_init) so rule coverage is captured even when no rules are added interactively during the session. (search for "tengu_shell_allow_rules_at_init")

The build it came inv2.1.166

5 Jun 2026 · 13 entries, this one is #13.

Either side of it

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--cloud
With a task description, create a new cloud session. With a session ID (session_... or cse_...) or a claude.ai/code URL, queue a message into that existing session instead, with -p. See send a follow-up message.
cli--remote
Deprecated alias for --cloud, including the existing-session form
flagtengu_shell_allow_rules_at_init
An analytics event, not a feature flag. Claude Code logs it once during session initialization with counts of the always-allow permission rules for its shell tools, keyed <source>_<tool>_<kind> where the source is userSettings, projectSettings, localSettings, flagSettings, cliArg or session and the kind is bare, scoped or dangerous_prefix, plus total_shell_allow_rules.

Is this right?