Every feature flag, and where it lived
2,081 feature flags One tick per build on this box, oldest on the left. A gap is a build the feature flag was not in.
State
This account
Anonymous
Compiled default
A is the one account this site reads, N the anonymous baseline, D what the release compiled in. 1,143 of 2,081 gates have been read at all: a run only records the gates its own release wrote about. Claude Code evaluates its gates on Anthropic's servers, so a reading of off can be a rollout this account sits outside of, and none of it says anything about your install. How to read these.
○ not in v2.1.308, ◇ we found no documentation describing it.
Feature flagWhat it doesSpan v2.1.138 → v2.1.308 Status Reading
tengu_cosmic_cookie ◇ Claude Code has a new remote switch, read by the code that manages terminal sessions, with no visible feature behind it yetv2.1.295 → v2.1.308 ◆in the build AND v2.1.295
tengu_cosmic_crayon ◇ No description from anybody.v2.1.299 ○gone AND v2.1.308
tengu_cosmic_lake ◇ Default false. When on, the rate-limit-warning notification (the warning shown as a usage limit gets close) is skipped when the limit status is allowed_warning and the limit type is five_hour. Warnings for other limit types still show.v2.1.282 → v2.1.308 ◆in the build never read
tengu_cosmic_shore ◇ Default true. When on, a shell command running in the background is stopped once it passes a deadline, capped at 2 hours (or BASH_MAX_TIMEOUT_MS if larger): a command started with run_in_background uses its timeout if given, and otherwise, or when a command is moved to the background later, the deadline is 30 minutes (or BASH_DEFAULT_TIMEOUT_MS if larger); the message telling Claude a command moved to the background can then say when it will be stopped. When off, or when the background deadline is disabled for the session, backgrounded commands get no such deadline, and commands started by Monitor never get it.v2.1.285 → v2.1.308 ◆in the build AND v2.1.308
tengu_cost_threshold_acknowledged ◇ The spend warning and resume prompt now queue with other dialogs instead of popping over your work.never mined ·never mined never read
tengu_cowork_auto_mode_include_allowed_write_mcp ◇ MCP tools that may act on a session's desktop now need approval each time, and remote-session MCP prompts cannot become always-allow rulesv2.1.212 → v2.1.308 ◆in the build AND v2.1.299
tengu_cowork_chrome_automode_default ◇ The terminal tab status toggle, Claude API tip and Chrome classifier default only moved; their gate fallbacks are unchangedv2.1.187 → v2.1.308 ◆in the build AND v2.1.296
tengu_cozy_dusk ◇ A new numeric remote-config gate was added with clamped bounds.v2.1.261 → v2.1.308 ◆in the build never read
tengu_cozy_eagle ◇ Some Claude in Chrome tools now ask for your permission rather than running at once, even with a whole-tool allow rulev2.1.290 → v2.1.308 ◆in the build AND v2.1.290
tengu_cozy_fern ◇ If an MCP tool asks to end the turn while a tool call in the same batch failed, Claude Code can now keep the turn goingv2.1.301 → v2.1.308 ◆in the build AND v2.1.302
tengu_cozy_kite ◇ Before a tool runs, Claude Code can wait for files still being staged, but only when a remote switch that defaults to off is onv2.1.292 → v2.1.308 ◆in the build AND v2.1.292
tengu_cozy_pixel ◇ A new fork_conversation control request lets a host app branch a session's history into a brand-new sessionv2.1.268 → v2.1.276 ○gone AND v2.1.277
tengu_cozy_teapot ◇ A remotely gated A/B test can loosen the bash-first system prompt wording.v2.1.271 → v2.1.306 ○gone AND v2.1.307
tengu_crimson_vector ◇ Default false. When on, and requests go to Anthropic's first-party API (the firstParty provider with no ANTHROPIC_BASE_URL or an Anthropic one), the default maximum base64 size for an image sent to the model rises from 5242880 bytes (5 MB) to 10485760 bytes (10 MB). A model whose own image limits set a maximum size keeps that value.v2.1.138 or earlier → v2.1.308 ◆in the build AND v2.1.308
tengu_cross_session_inbound_changed ◇ A settings row for handling messages from your other sessions exists but is hidden here.never mined ·never mined never read
tengu_cuddly_willow ◇ Relayed messages from a new inbound source count as a human turn by default.v2.1.233 → v2.1.308 ◆in the build AND v2.1.280
tengu_curious_lake ◇ Delete commands like rd or del run through cmd.exe are now blocked when they target a drive root, a top folder or homev2.1.304 ○gone AND v2.1.283
tengu_curious_river ◇ In Anthropic cloud sessions, a running MCP task stops keeping its cloud container up after a set number of hours, 168 by defaultv2.1.305 → v2.1.308 ◆in the build AND v2.1.305
tengu_curious_tower ◇ New gated 'tether' system can thread API requests together server-side instead of resending full context each turnv2.1.265 → v2.1.308 ◆in the build AND v2.1.296
tengu_curious_tower_stateless_models ◇ New gated 'tether' system can thread API requests together server-side instead of resending full context each turnv2.1.265 → v2.1.308 ◆in the build AND v2.1.265
tengu_curried_trinket ◇ No description from anybody.v2.1.290 → v2.1.308 ◆in the build AND v2.1.308
tengu_daemon_control ◇ An analytics event, not a feature flag. Claude Code logs it from the claude daemon start, restart, stop and uninstall subcommands with the outcome: op_start, op_restart, op_stop or op_uninstall plus ok, and depending on the path launcher, reachable, reaped or holderUnverified.v2.1.138 or earlier → v2.1.241 ○gone never read
tengu_daemon_install ◇ An analytics event, not a feature flag. Claude Code logs it from claude daemon install with ok: on a refusal it names the reason (disabled, launcher, foreground, or holderAlive with holderUnverified or holderUnknownOrigin), a failed service install logs ok: false alone, and a successful install records whether the daemon was reachable afterwards. claude daemon start and restart also log it with disabled: true when those subcommands are disabled.v2.1.138 or earlier → v2.1.241 ○gone never read
tengu_daemon_refuse_stale_upgrade ◇ Default true. When the background daemon's supervisor sees that the Claude Code binary it runs from was replaced by an older build (judged by the build timestamps in the two build names), it refuses the self-restart it would otherwise do to pick up the new binary, keeps the running build and logs refusing self-restart for upgrade. When off, that check is skipped and the upgrade restart goes on through the usual checks.v2.1.203 → v2.1.308 ◆in the build never read
tengu_daemon_stale_lock_replaced ◇ Replacing a stale daemon lock now reports the proof type, holder age and whether it ran a different version.never mined ·never mined never read
tengu_daemon_startup_crash ◇ The background daemon now restores Cloud gateway sign-in early at startupv2.1.138 or earlier → v2.1.304 ○gone never read
tengu_daemon_upgrade_defer_busy ◇ The background service waits for your turn to finish before restarting for an upgrade.v2.1.248 → v2.1.308 ◆in the build AND v2.1.300
tengu_daemon_upgrade_deferred_busy ◇ The background service waits for your turn to finish before restarting for an upgrade.never mined ·never mined never read
tengu_daemon_upgrade_respawn_unreachable ◇ An analytics event, not a feature flag. Claude Code logs it when the daemon detects an upgrade and re-spawns itself, and the successor process spawns but does not become reachable in time. The field stderr_captured says whether any of the successor's stderr was captured.v2.1.203 → v2.1.241 ○gone never read
tengu_dapper_acorn ◇ A new remotely controlled switch is off by default and never applies to organisations under the HIPAA policyv2.1.290 → v2.1.308 ◆in the build AND v2.1.290
tengu_dapper_brooks ◇ Remote Control can download up to 16 attachments ahead of time, before the message that uses them arrivesv2.1.281 → v2.1.308 ◆in the build AND v2.1.281
tengu_dapper_cupcake ◇ The setting that controls artifacts beside tool results is now CLAUDE_CODE_DAPPER_CUPCAKE, and the old CLAUDE_CODE_SQUISHY_NEWT is ignoredv2.1.301 → v2.1.308 ◆in the build AND v2.1.301
tengu_dapper_dawn ◇ The shadow logging that measures idle sessions now records when Claude Code starts and stops waiting for your input, not only when work runsv2.1.251 → v2.1.308 ◆in the build AND v2.1.283
tengu_dapper_dusk ◇ Claude Code adds several new remotely controlled switches whose purpose is not yet visiblev2.1.299 → v2.1.308 ◆in the build AND v2.1.299
tengu_dapper_lagoon ◇ An environment variable overrides whether something counts as first-party.v2.1.251 → v2.1.276 ○gone AND v2.1.251
tengu_dapper_platypus ◇ A relay-marked worker whose relay can no longer be used now makes its first command wait for MCP servers like an ordinary workerv2.1.286 → v2.1.308 ◆in the build AND v2.1.301
tengu_dapper_truffle ◇ Auto mode's check of allowed MCP write tools now accepts rules from a command and adds a server-side decision path that is off by defaultv2.1.299 → v2.1.308 ◆in the build AND v2.1.299
tengu_dash_flame ◇ No description from anybody.v2.1.219 → v2.1.308 ◆in the build AND v2.1.308
tengu_dazzling_floyd ◇ You can type /review instead of /code-review, and pass a PR number as the target.v2.1.223 → v2.1.241 ○gone AND v2.1.246
tengu_dazzling_garden ◇ Three new remote-bridge switches appear, covering a retry after a rejected token refresh and two unread ones.v2.1.238 → v2.1.308 ◆in the build AND v2.1.238
tengu_dead_probe_ ◇ Temporary probes that checked whether old code paths still ran have been deleted; behaviour is unchanged.never mined ·never mined never read
tengu_dead_probe_adopt_ticks_token ◇ One-off counters now show which old code paths are still being used, so they can be removed.never mined ·never mined never read
tengu_dead_probe_autoupdater_status ◇ Very old config files with legacy updater values now migrate to an unknown install method.never mined ·never mined never read
tengu_dead_probe_bg_legacy_op ◇ Each older background-session operation reports once, showing which legacy paths are still used.never mined ·never mined never read
tengu_dead_probe_daemon_origin_auto ◇ An analytics event, not a feature flag. Claude Code logs it, at most once per site per process, when it meets the daemon origin value auto: when parsing --origin auto (which is treated as transient), when formatting the daemon status, and in the daemon status output. The field site names which of the three it was.v2.1.208 → v2.1.220 ○gone never read
tengu_dead_probe_enable_auto_mode_flag ◇ Five more leftover diagnostic probes were deleted, with no change to what you see.never mined ·never mined never read
tengu_dead_probe_hook_updated_mcp_tool_output ◇ Five more leftover diagnostic probes were deleted, with no change to what you see.never mined ·never mined never read
tengu_dead_probe_include_coauthored_by ◇ One-off counters now show which old code paths are still being used, so they can be removed.never mined ·never mined never read
tengu_dead_probe_install_counts_cleanup ◇ Five more leftover diagnostic probes were deleted, with no change to what you see.never mined ·never mined never read
tengu_dead_probe_iterm2_crash_restore ◇ Two new counters cover swept placeholder bridge sessions and iTerm2 crash-restore probes.never mined ·never mined never read
tengu_dead_probe_mcp_subsec_timeout ◇ Most of the one-shot probes checking whether old code paths still run were removed.never mined ·never mined never read
tengu_dead_probe_pinned_sidecar ◇ Most of the one-shot probes checking whether old code paths still run were removed.never mined ·never mined never read
tengu_dead_probe_plugin_toplevel_experimental ◇ Most of the one-shot probes checking whether old code paths still run were removed.never mined ·never mined never read
tengu_dead_probe_preserved_segment ◇ Temporary probes that checked whether old code paths still ran have been deleted; behaviour is unchanged.never mined ·never mined never read
tengu_dead_probe_speculation_overlay ◇ Five more leftover diagnostic probes were deleted, with no change to what you see.never mined ·never mined never read
tengu_dead_probe_taskstop_shell_id ◇ Five more leftover diagnostic probes were deleted, with no change to what you see.never mined ·never mined never read
tengu_dead_probe_tool_alias_exec ◇ Five more leftover diagnostic probes were deleted, with no change to what you see.never mined ·never mined never read
tengu_dead_probe_voice_enabled_flat ◇ Five more leftover diagnostic probes were deleted, with no change to what you see.never mined ·never mined never read
tengu_declared_tool_set_held ◇ A new event tracks how often a session has to defer late tools or redeclare dropped ones.never mined ·never mined never read
tengu_declared_tools_dropped_at_compaction ◇ Claude Code can now drop unused MCP tools from a session's declared-tools list when compacting the conversationnever mined ·never mined never read
tengu_deep_feather ◇ A new remote flag, on by default, reassembles split message-tool inputs when they are read back.v2.1.236 → v2.1.308 ◆in the build AND v2.1.236
tengu_deep_ocean_current ◇ No description from anybody.never mined ·never mined never read
tengu_deep_shore ◇ A remote switch can make Claude Code wait a short, limited time for some data before each model requestv2.1.288 → v2.1.308 ◆in the build AND v2.1.288
tengu_deep_starlight ◇ Whole-PDF reads can skip a page-image render that only fed telemetry, and PDF renders can now be cancelledv2.1.281 → v2.1.306 ○gone AND v2.1.307
tengu_defer_cap_ms ◇ Backgrounding a task now reads the terminal title and agent from shared stores.v2.1.195 → v2.1.308 ◆in the build never read
tengu_deferred_stub_tool ◇ Default true, read once per session and then kept. When on and deferred tool loading is in use, a request's tool list gains a tool named DeferredToolPlaceholder with defer_loading set, described as Reserved placeholder that keeps deferred tool loading active; never call this tool., unless one is already there. It is never added under HIPAA restrictions, or while CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS is set and tool search is not forced on.v2.1.207 → v2.1.308 ◆in the build AND v2.1.308
tengu_deferred_tools_pool_change ◇ Deferred-tool telemetry now tracks resurfaced tools and whether tool search is unavailablenever mined ·never mined never read
tengu_delegated_quail ◇ A background model-catalog comparison check now always has network access, though the feature stays off by defaultv2.1.251 → v2.1.308 ◆in the build AND v2.1.283
tengu_delightful_hamster ◇ Claude Code drops a plugin's MCP server that matches an ineligible connector, unless a remote switch, off by default, keeps itv2.1.307 → v2.1.308 ◆in the build AND v2.1.307
tengu_destructive_command_warning ◇ The destructive-command warning now reads the real command, but it stays off unless the feature flag is on.v2.1.138 or earlier → v2.1.308 ◆in the build AND v2.1.290
tengu_device_bash_output_limit ◇ Device bash limit and timeout events dropped their session-matching field.never mined ·never mined never read
tengu_device_bash_served ◇ The local-command tool refuses to run unless your sandbox is strict and fully confining.never mined ·never mined never read
tengu_device_bind_account ◇ A token from the wrong account now says so and tells you to log out.never mined ·never mined never read
tengu_device_bind_attach ◇ A remote session can be pinned to one device, refusing attach from anywhere else.never mined ·never mined never read
tengu_device_bind_failed ◇ Cloud sessions can be bound to your machine so local tools only run there, currently gated off.never mined ·never mined never read
tengu_device_bind_prepared ◇ Remote sessions can be tied to the exact machine that started them using a per-account signing key.never mined ·never mined never read
tengu_device_bind_skipped ◇ Cloud sessions can be bound to your machine so local tools only run there, currently gated off.never mined ·never mined never read
tengu_device_bind_title_latched ◇ The automatic session rename after device binding is now signed.never mined ·never mined never read
tengu_device_bridge_connect_frame ◇ A machine attached to a cloud session but running nothing now advertises itself as idle.never mined ·never mined never read
tengu_device_bridge_heartbeat_unsupported ◇ The device bridge reports its whole connection lifecycle, but none of it fires yet.never mined ·never mined never read
tengu_device_bridge_muted ◇ The device bridge can be muted at runtime, withholding all but one tool and device announcement.never mined ·never mined never read
tengu_device_bridge_reannounce ◇ Device bridge re-announce events now record reason, outcome and drain timingnever mined ·never mined never read
tengu_device_bridge_reannounce_contended ◇ Device bridge re-announce events now record reason, outcome and drain timingnever mined ·never mined never read
tengu_device_bridge_skipped ◇ The device bridge is skipped entirely when the host's account UUID doesn't match the stored one.never mined ·never mined never read
tengu_device_bridge_started ◇ The device bridge reports its whole connection lifecycle, but none of it fires yet.never mined ·never mined never read
tengu_device_hook_served ◇ Six telemetry events for machine-run cloud hooks exist but cannot fire in this build.never mined ·never mined never read
tengu_device_hook_template_run ◇ If a device hook template cannot install, the tools it guarded are now denied rather than allowed.never mined ·never mined never read
tengu_device_hook_template_upload ◇ Three more telemetry shapes cover hook template runs, uploads and expiring registrations.never mined ·never mined never read
tengu_device_hooks_client_register ◇ Six telemetry events for machine-run cloud hooks exist but cannot fire in this build.never mined ·never mined never read
tengu_device_hooks_consent_notice ◇ Six telemetry events for machine-run cloud hooks exist but cannot fire in this build.never mined ·never mined never read
tengu_device_hooks_headless_off ◇ Cloud sessions can run your local hooks once you agree on this machine; run /hooks to decide.never mined ·never mined never read
tengu_device_hooks_lapse_line ◇ Six telemetry events for machine-run cloud hooks exist but cannot fire in this build.never mined ·never mined never read
tengu_device_hooks_reach_pinned ◇ Six telemetry events for machine-run cloud hooks exist but cannot fire in this build.never mined ·never mined never read
tengu_device_hooks_source_pinned ◇ Six telemetry events for machine-run cloud hooks exist but cannot fire in this build.never mined ·never mined never read
tengu_device_reenroll ◇ Claude Code can now re-register a device when its saved key conflicts with a stored onenever mined ·never mined never read
tengu_device_tool_refused ◇ Tools on your machine refuse calls from a cloud session other than the one being served.never mined ·never mined never read
tengu_dialog_waiting_in_transcript ◇ New automatic prompts appear: a first-time auto mode warning, a spending threshold dialog and a worktree tip.never mined ·never mined never read
tengu_dir_sync_anchor ◇ A cloud pull now stashes uncommitted files it overwrites into .claude-cloud-trash and tells you where.never mined ·never mined never read
tengu_dir_sync_apply_start ◇ A directory can be seeded with a listed set of files, skipping anything already there.never mined ·never mined never read
tengu_dir_sync_barrier ◇ Cross-machine file sync now reports five new events covering disagreement, mid-turn sync and file handoff.never mined ·never mined never read
Nothing on this page matches that. Press Enter to search every feature flag.