Feature flags, all 2,081.

tengu_bash_allowlist_strip_all ◇ Default false. Its value is recorded as stripAllBashFlag on the tengu_auto_mode_decision telemetry event sent when the auto mode classifier reviews a tool call; the fast-path and subagent-handoff decision events do not carry it, and no other code reads the flag in this version.v2.1.138 or earlier → v2.1.191 ○gone never read tengu_bash_ast_too_complex ◇ Bash's 'too complex to check' read-block guard now applies via a general table covering more refusal reasons, not just one hardcoded casenever mined ·never mined never read tengu_bash_command_clamp_denied ◇ If a clamped agent's permission check crashes, the shell command is denied rather than allowed.never mined ·never mined never read tengu_bash_dangerous_rm_too_complex ◇ The dangerous-rm safety check for bash commands can now be extended with an extra custom checknever mined ·never mined never read tengu_bash_security_check_triggered ◇ No description from anybody.never mined ·never mined never read tengu_bash_task_ack ◇ Backgrounded shell commands may return a structured task record instead of raw output.never mined ·never mined never read tengu_bash_task_delivered ◇ Finished background tasks now report whether their output was spliced back in or lost.never mined ·never mined never read tengu_bash_tool_command_executed ◇ Bash/PowerShell telemetry and sandbox checks now track whether the user typed the command directly.never mined ·never mined never read tengu_bash_tool_command_failed ◇ Bash tool telemetry now records a detailed breakdown of each command's shapenever mined ·never mined never read tengu_bedrock_upgrade_check ◇ Bedrock and Vertex now share one check for outdated pinned model variables.never mined ·never mined never read tengu_began_setup ◇ Onboarding now also treats a 'gateway' authentication setup as equivalent to OAuth for its flownever mined ·never mined never read tengu_bergotte_lantern ◇ No description from anybody.never mined ·never mined never read tengu_bg_adopt_upgrade_respawn ◇ Background sessions stop needlessly restarting when your running build is already newer.never mined ·never mined never read tengu_bg_agent_action ◇ Background-agent telemetry no longer records which agent template was usednever mined ·never mined never read tengu_bg_attach_outcome ◇ Background attach events now record cold starts, surface and first frame details.never mined ·never mined never read tengu_bg_attach_stall_ms ◇ Default 5000 (milliseconds). How long attaching to a background session may wait for it to redraw before Claude Code restarts the session with Session not responding; after two such restarts it gives up, prints Session keeps stalling at startup. and kills the session. 0 turns the restart off; any other value is raised to at least 2000, or 12000 when a background-session launcher is configured.v2.1.138 or earlier → v2.1.308 ◆in the build AND v2.1.308 tengu_bg_attach_upgrade ◇ Default true. Gates the background-session supervisor's prewarming: restarting idle background sessions whose recorded Claude Code version is stale onto the running version, in one delayed burst once the supervisor is ready and up to tengu_bg_prewarm_per_sweep (default 3) per periodic sweep while memory is not low. Sessions launched in exec mode are skipped and a session on a newer version is not downgraded. Turning it off stops prewarming; the sweep still restarts sessions in its pinned set.v2.1.162 → v2.1.308 ◆in the build never read tengu_bg_classifier_config ◇ Background classifier gets a new, currently inactive setting to control how much recent conversation text it quotesv2.1.138 or earlier → v2.1.308 ◆in the build never read tengu_bg_classify ◇ A new 'Projects' recap mode for the background classifier can summarize thread status, currently unread/offnever mined ·never mined never read tengu_bg_daemon_binary_takeover ◇ The background daemon can now retire a same-version instance; build is 2.1.248.never mined ·never mined never read tengu_bg_daemon_spawn_failed ◇ An analytics event, not a feature flag. Claude Code logs it when it fails to spawn the background daemon: when spawning a transient daemon with daemon run --origin transient errors, when a configured agent launcher's daemon never becomes reachable, and when the daemon's upgrade self-respawn fails to spawn. Fields include errno_enoent, errno_eacces, errno, launcher_configured, failed_stage or respawn depending on the site.v2.1.138 or earlier → v2.1.241 ○gone never read tengu_bg_daemon_spawn_reinstall_wait ◇ Starting the background helper during an npm reinstall now waits and retries instead of failing.never mined ·never mined never read tengu_bg_dispatch_fallback ◇ Background dispatch failures now distinguish a daemon that started but couldn't launch Claude Code.never mined ·never mined never read tengu_bg_dispatch_rejected ◇ The background daemon now records why it refused a queued dispatch file.never mined ·never mined never read tengu_bg_imark_malformed ◇ Background sessions now send readiness marks so attaching knows when a session is actually interactive.never mined ·never mined never read tengu_bg_pty_unavailable ◇ An analytics event, not a feature flag. Claude Code logs it when a background session cannot be started because no pseudo-terminal spawner is available, marking the job crashed with the detail Bun.Terminal unavailable (running under Node?); it carries the job's short id.never mined ·never mined never read tengu_bg_ptyhost_zombie ◇ Background sessions whose terminal process died are now killed and marked failed instead of hanging.never mined ·never mined never read tengu_bg_retire_grace_bridged_min ◇ A prompt-and-context experiment switch was renamed and four other switches disappeared entirely.v2.1.149 → v2.1.245 ○gone never read tengu_bg_retired ◇ A background worker can now be retired purely for running a stale CLI version, with new retirement causes recorded.never mined ·never mined never read tengu_bg_revival_guard ◇ Default true. Applies when a background session's worker process crashes and is respawned. When on, a respawn that resumes a transcript with messages also gets CLAUDE_CODE_RESUME_PROMPT set (if not already set) to a note saying the session was restarted automatically and Claude should re-verify anything time-sensitive, plus CLAUDE_CODE_RESUME_INTERRUPTED_TURN_MAX_AGE_MS of one hour for sessions with interactive lineage, and each scheduled respawn first reads the session's record on disk and is skipped when that record already shows a finished state with no queued prompt. When off, only CLAUDE_CODE_RESUME_INTERRUPTED_TURN=1 is set on such a respawn and the on-disk check is not made.v2.1.211 → v2.1.308 ◆in the build never read tengu_bg_roster_orphan_adopted ◇ Recovering a stray background agent entry now records that it happened, so gaps are traceable.never mined ·never mined never read tengu_bg_session_id_taken ◇ Background sessions that hit an already-claimed session id now fail with a clear dimmed notice.never mined ·never mined never read tengu_bg_spare_claim_fail ◇ Background session records can be flagged as spare, but nothing in this build decides when a spare gets spawned.never mined ·never mined never read tengu_bg_spare_enable ◇ Default true. Lets the background-session dispatcher keep a warm spare worker process started ahead of time (not on Windows) and hand it to the next dispatched session whose launch mode is not exec, provided the spare was started by the same Claude Code version. Turning it off disposes any existing spare and stops spares from being started or claimed.v2.1.138 or earlier → v2.1.308 ◆in the build never read tengu_bg_spawn_cwd_gone ◇ An analytics event, not a feature flag. Claude Code logs it when a background session cannot start because its working directory no longer exists or is not accessible, with the job's short id, the attempt number and via. With via of dispatch the daemon refuses the job; with cold, spare or boot the spawn path marks the job crashed and it is not respawned.never mined ·never mined never read tengu_bg_state_read_recovered ◇ Background state reads retry on transient errors instead of failing immediately.never mined ·never mined never read tengu_bg_state_read_transient ◇ Background job state read failures now report themselves once per job instead of silently falling back to a cache.never mined ·never mined never read tengu_bg_worker_exit ◇ A background worker that dies before starting is reported as a crash, not silence.never mined ·never mined never read tengu_binary_content_persisted ◇ Files Claude saves from web fetches, artifacts and binary tool output are now tracked in session state.never mined ·never mined never read tengu_binary_download_success ◇ Updates can arrive as a compressed build, so downloads get smaller with no setting to change.never mined ·never mined never read tengu_binary_lollipop ◇ Claude Code now contains the name of a new server-controlled switch, but nothing yet shows what it controlsv2.1.290 → v2.1.308 ◆in the build never read tengu_birch_kettle ◇ Default false. Enables the bundled claude-code-docs skill, which answers questions about Claude Code's own commands, flags, settings, hooks and other features, can be invoked by the user with a [question] argument, and is allowed Read, Grep, Glob and WebFetch limited to code.claude.com and platform.claude.com. The skill is enabled only when this flag is on and its registration was not marked disabled.v2.1.154 → v2.1.308 ◆in the build AND v2.1.308 tengu_brass_lantern ◇ New startup telemetry tracks managed-config readiness and an optional live identity checkv2.1.271 → v2.1.289 ○gone never read tengu_brass_sled ◇ Default false. When on, the PowerShell tool's prompt gets a "Developer tools verified on this machine's PATH" line listing the build and dev tools Claude Code detected, telling Claude that a tool missing from the list is likely not installed and should be checked with Get-Command first; on Windows it adds a note that the MSVC toolchain (cl, nmake, msbuild) is only on PATH inside a Visual Studio developer shell. The line is left out when no tools were detected.v2.1.198 → v2.1.308 ◆in the build AND v2.1.308 tengu_breezy_horizon ◇ You can swap the model a request uses by setting an environment variable, or the server can do it.never mined ·never mined never read tengu_brick_follow ◇ Default false. When on, or when CLAUDE_CODE_VOICE_FORWARD_INTERIMS_TYPED is set, the voice dictation speech-to-text WebSocket is opened with forward_interims=typed added to its query string. The flag's value is also passed to the VS Code extension in its experiment_gates notification.v2.1.141 → v2.1.308 ◆in the build AND v2.1.308 tengu_bridge_env_reregister ◇ Remote control re-registers and reattaches your sessions if the server forgets this machine.never mined ·never mined never read tengu_bridge_fatal_error ◇ Remote Control now gives a clearer fatal error when it can't renew its connection credentialnever mined ·never mined never read tengu_bridge_host_profile_collect ◇ Forced-ask permission decisions now include a suggested standing allow rule where applicable.never mined ·never mined never read tengu_bridge_message_received ◇ Claude Code's internal message bridge now ignores certain 'fork display frame' messages before processing themnever mined ·never mined never read tengu_bridge_owner_changed ◇ A live remote session now shuts down if you sign into a different account mid-session.never mined ·never mined never read tengu_bridge_placeholder_sweep ◇ Default true. Gates Remote Control placeholder bookkeeping: recording placeholder session ids in the replBridgePlaceholders config map (newest 20 kept), and a once-per-process sweep, 15 seconds after start, that looks at records older than 5 minutes whose owning Claude Code process is no longer running, archives a placeholder session that was never updated after creation, and drops records whose session is gone, was used, was archived, or is older than 30 days. false turns both off.v2.1.217 → v2.1.280 ○gone AND v2.1.308 tengu_bridge_placeholder_used_session ◇ Two new counters cover swept placeholder bridge sessions and iTerm2 crash-restore probes.never mined ·never mined never read tengu_bridge_rc_child_idle_exit_ms ◇ More conditions now trigger a session-tag prefetch before spawning a Remote Control bridge workerv2.1.273 → v2.1.308 ◆in the build AND v2.1.308 tengu_bridge_repl_auth_revive ◇ After you log back in, Remote Control can turn itself back on without you re-running the command.never mined ·never mined never read tengu_bridge_repl_auto_disabled ◇ Running /clear no longer disconnects the editor bridge; it follows you onto the new session.never mined ·never mined never read tengu_bridge_repl_connect_timeout ◇ Remote connection timeouts now record whether they happened during recovery or a token refresh.never mined ·never mined never read tengu_bridge_repl_events_carried_over ◇ Undelivered events now carry over when the remote bridge rebuilds its connection.never mined ·never mined never read tengu_bridge_repl_started ◇ Remote bridge session-start telemetry now includes a ccr_session_id fieldnever mined ·never mined never read tengu_bridge_repl_teardown ◇ Session teardown reporting now distinguishes two different kinds of skipped cleanup.never mined ·never mined never read tengu_bridge_repl_v2_cse_shim_enabled ◇ Default true. When on, a session ID beginning cse_ is rewritten to the session_ form before it goes into the /v1/sessions/<id> URL of the code-session v1 compatibility path. When off, the cse_ ID is used unchanged.v2.1.138 or earlier → v2.1.308 ◆in the build never read tengu_bridge_repl_ws_closed ◇ Remote bridge socket closes now record a cause alongside the numeric code.never mined ·never mined never read tengu_bridge_repl_ws_connected ◇ Remote bridge reconnects record how many times credentials were re-minted and where a reattach came from.never mined ·never mined never read tengu_bridge_restored_pointer_takeover ◇ Resuming a session another process still holds now tells you to run /remote-control to take it over.never mined ·never mined never read tengu_bridge_server_config_applied ◇ Remote Control workers could receive MCP config and prompts from the daemon, but no session does.never mined ·never mined never read tengu_bridge_server_config_rejected ◇ Remote Control workers could receive MCP config and prompts from the daemon, but no session does.never mined ·never mined never read tengu_bridge_token_absence_classified ◇ When a background bridge worker can't get your login token, it now records exactly why.never mined ·never mined never read tengu_bridge_vivid ◇ No description from anybody.v2.1.142 → v2.1.259 ○gone never read tengu_brief_mode_enabled ◇ /brief is hidden by server config, but brief mode still works via an environment variable.never mined ·never mined never read tengu_brook_heron ◇ Extra per-model guidance can be added to your session, but nothing supplies it here.never mined ·never mined never read tengu_brook_heron_applied ◇ Extra per-model guidance can be added to your session, but nothing supplies it here.never mined ·never mined never read tengu_bug_report_description ◇ Bug report data now goes through the same scrubbing as other telemetry before being sent.never mined ·never mined never read tengu_bug_report_failed ◇ More analytics fields get cleaned before sending, and some events carry extra context.never mined ·never mined never read tengu_bug_report_submitted ◇ Bug report data now goes through the same scrubbing as other telemetry before being sent.never mined ·never mined never read tengu_builtin_mcp_toggle ◇ MCP server names are now redacted in toggle telemetry events.never mined ·never mined never read tengu_c4e_slash_upsell_shown ◇ Claude for Enterprise upsell message now differs for users who are fully signed out versus just missing an enterprise orgnever mined ·never mined never read tengu_cache_heartbeat_shadow ◇ Logic measuring how long you've been idle logs what a cache stop would do without doing it.never mined ·never mined never read tengu_cache_warming_request ◇ No description from anybody.never mined ·never mined never read tengu_canary ◇ Default {}. Its external field, when it holds a valid version string, names a canary release for the native installer: when an update asks for latest and the canary is newer than the version latest resolved to, the canary is installed instead. A canary above the configured maxVersion is not applied.v2.1.138 or earlier → v2.1.308 ◆in the build AND v2.1.308 tengu_cc_ce_migrate_notice_shown ◇ A startup banner pitching Claude Enterprise to org admins exists but no one sees it by default.never mined ·never mined never read tengu_ccr_bundle_max_bytes ◇ Default null, which means 104857600 bytes (100 MiB). The size cap for the git bundle built to upload a local repository to a cloud session: bundle tiers larger than the cap are skipped in favour of narrower ones, and when even the last tier exceeds it the upload fails with "Repo is too large to bundle". Twice the cap also limits the bytes staged into the work-in-progress stash commit that goes into the bundle.v2.1.138 or earlier → v2.1.308 ◆in the build AND v2.1.308 tengu_ccr_bundle_upload ◇ Most of this release's changed code is the build system moving modules, not features changing.never mined ·never mined never read tengu_ccr_delta_rehydrate ◇ Default false. Used when resuming a remote (CCR v2) session from its internal events. When off, the resume records the fallback reason client-gated and reads the events without a starting event id. When on, it looks up a stored event id for the session and, if that id appears in the last 64 KiB of the local transcript, passes it to the internal event reader so reading starts from that event; otherwise it falls back with the reason no-sidecar or tip-not-in-tail.v2.1.181 → v2.1.259 ○gone AND v2.1.308 tengu_ccr_disk_watchdog ◇ A new gated background watchdog can warn or take action when disk space runs lowv2.1.268 → v2.1.308 ◆in the build never read tengu_ccr_init_park_report ◇ A background worker can now report at startup that it needs your attention rather than just idle.never mined ·never mined never read tengu_ccr_internal_events_dropped ◇ The internal-event uploader takes tunable failure, batch-size and timeout limits and reports dropped batches.never mined ·never mined never read tengu_ccr_memory_watchdog ◇ No description from anybody.v2.1.304 → v2.1.308 ◆in the build never read tengu_ccr_overlay_bundle ◇ A cloud session can start from your local commits instead of always pulling the remote copy.never mined ·never mined never read tengu_ccr_plugins_turn_start_check_enabled ◇ No description from anybody.v2.1.299 → v2.1.306 ○gone AND v2.1.308 tengu_ccr_preserved_event_ids_clamped ◇ Compaction now trims the saved conversation payload to match the preserved message list, avoiding mismatches.never mined ·never mined never read tengu_cd_command ◇ /cd now re-points transcript, settings, hooks and skills in one pass and reports anything left behind.never mined ·never mined never read tengu_cedar_ember ◇ Hidden /limit-reset command lets Max/Pro users consume an available usage-limit reset immediatelyv2.1.271 → v2.1.308 ◆in the build never read tengu_cedar_ember_ ◇ A new 'Cedar Ember' rate-limit grant offer can now appear as a notice bar messagenever mined ·never mined never read tengu_cedar_ember_asked ◇ New /limit-reset command lets you manually claim a one-time reset of your rate limitnever mined ·never mined never read tengu_cedar_ember_confirmed ◇ New /limit-reset command lets you manually claim a one-time reset of your rate limitnever mined ·never mined never read tengu_cedar_ember_result ◇ New /limit-reset command lets you manually claim a one-time reset of your rate limitnever mined ·never mined never read tengu_cedar_ember_selected ◇ New /limit-reset command lets you manually claim a one-time reset of your rate limitnever mined ·never mined never read tengu_cedar_ember_shown ◇ New /limit-reset command lets you manually claim a one-time reset of your rate limitnever mined ·never mined never read tengu_cedar_ember_wall ◇ New /limit-reset command lets you manually claim a one-time reset of your rate limitnever mined ·never mined never read tengu_cedar_hollow_7m ◇ Default {}. When the current model resolves to claude-opus-4-8, a model field in this object sets the model the auto mode permission classifier uses, ahead of tengu_auto_mode_config.model. With any other model, or with no model field, the classifier uses tengu_auto_mode_config.model and then the current model.v2.1.154 → v2.1.165 ○gone AND v2.1.308