Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One family

Feature flags, all 2,081.

GrowthBook gates the client evaluates on startup. Most of what ships is behind one of these before it is announced.

Feature flags2,081seen across 149 builds
In v2.1.308889the newest inventory on disk
Gone314in an earlier build, not in the newest
Described0have a line in Anthropic's documentation
No docs line2,081no line in the documentation we hold

Every feature flag, and where it lived

938 of 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.

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_compact_line_prefix_killswitch ◇ No description from anybody.never mined ·never mined never read tengu_compact_preserved_unanchored ◇ Transcript saving and cleanup logic is consolidated in one place; nothing changes for you.never mined ·never mined never read tengu_compact_replaced_by_hook ◇ Compaction now records when a hook fully replaced Claude Code's own summarization logicnever mined ·never mined never read tengu_compact_streaming_retry ◇ No description from anybody.never mined ·never mined never read tengu_concurrent_onquery_detected ◇ An analytics event, not a feature flag. Claude Code logs it, with no fields, when a new query is submitted while another query is still running; the new query does not run, and its user prompts (other than some internal and notification messages) are put back on the input queue.never mined ·never mined never read tengu_concurrent_sessions ◇ An analytics event, not a feature flag. Claude Code logs it at startup, after registering the session and counting the live sessions in its session registry, when that count is 2 or more; it carries num_sessions.never mined ·never mined never read tengu_config_auth_loss_prevented ◇ A second global-config writer goes through the storage backend with better corruption handling.never mined ·never mined never read tengu_config_auto_repaired ◇ An analytics event, not a feature flag. Claude Code logs it when a locked save of the global config re-reads the config file, hits a parse error, and rewrites the file from its cached config instead. It carries file_size_before (the size of the unparseable file) and had_cached_auth (whether the cached config had an oauthAccount or hasCompletedOnboarding: true).never mined ·never mined never read tengu_config_changed ◇ Plugin-provided settings now appear in /config, with their values redacted in telemetrynever mined ·never mined never read tengu_config_fallback_skipped_contention ◇ Saving or deleting config now retries with backoff when the lock is held instead of failing outright.never mined ·never mined never read tengu_config_lock_contention ◇ The settings lock contention counter stops counting unrelated storage failures.never mined ·never mined never read tengu_config_parse_error ◇ Keychain lookups fail quietly instead of crashing, and unparseable config files now get reported.never mined ·never mined never read tengu_config_stale_write ◇ A second global-config writer goes through the storage backend with better corruption handling.never mined ·never mined never read tengu_content_block_healed ◇ A malformed response block is repaired or dropped rather than crashing your session.never mined ·never mined never read tengu_context_tip_classifier_outcome ◇ An analytics event, not a feature flag. Claude Code logs it each time the context tips classifier (a model call with query source context_tip_classifier) finishes, with outcome one of tip, tip_ineligible, no_tip, parse_failure, error or outer_error. Other fields, when present: classifierLogId, durationMs, eligibleIds, featureId, inputTokens, cachedInputTokens, outputTokens and error details.never mined ·never mined never read tengu_continue ◇ claude -p --continue now says a matching session is running in the background instead of silently finding nothing.never mined ·never mined never read tengu_conversation_forked ◇ An analytics event, not a feature flag. Claude Code logs it after it forks the current conversation into a new branch session and saves that session's title (by default the first prompt followed by (Branch) or (Branch N)). It carries message_count and has_custom_title.never mined ·never mined never read tengu_conversation_rewind ◇ Compaction cleanup and rewind both notify a shared hook with a reason string.never mined ·never mined never read tengu_convolute_arcades_retry ◇ A hidden, server-controlled fallback path can now retry refused model turns under different, less visible telemetry namesnever mined ·never mined never read tengu_convolute_arcades_tools ◇ A hidden, server-controlled fallback path can now retry refused model turns under different, less visible telemetry namesnever mined ·never mined never read tengu_coordinator_panel ◇ No description from anybody.v2.1.157 → v2.1.308 ◆in the build never read tengu_copper_kestrel ◇ Default true. Gates effort changes over Remote Control: when on, a connected client can set effortLevel through apply_flag_settings and the session reports its effort to the bridge as effort_level metadata. When off, such a request fails with effort changes over Remote Control are turned off.v2.1.234 → v2.1.308 ◆in the build never read tengu_copper_lantern ◇ Default false. A recall switch for the Claude Code background daemon when it runs as an installed service: the supervisor checks it on each poll, and when it is on it logs service recall flag set, stops its workers, shuts down with cause service_recall and uninstalls the service. A daemon started as a transient process ignores it.v2.1.138 or earlier → v2.1.308 ◆in the build never read tengu_coral_whistle ◇ No description from anybody.never mined ·never mined never read 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_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_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_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_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_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_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_ocean_current ◇ No description from anybody.never mined ·never mined never read 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_tools_pool_change ◇ Deferred-tool telemetry now tracks resurfaced tools and whether tool search is unavailablenever mined ·never mined never read 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 tengu_dir_sync_between_tools_publish ◇ Directory-sync publish telemetry now tracks how long a sync was held before sendingnever mined ·never mined never read tengu_dir_sync_between_tools_take_in ◇ Cloud sessions can pull in your latest local edits between tool calls, not just at turn edges.never mined ·never mined never read tengu_dir_sync_direct_upload ◇ Directory sync can upload straight to a file store when the server offers that route.never mined ·never mined never read tengu_dir_sync_first_turn_hold ◇ Your first turn now waits for the initial directory sync, and deletions and nested repos are reported.never mined ·never mined never read tengu_dir_sync_first_upload_build ◇ An analytics event, not a feature flag. Claude Code logs it whenever an attempt to build the first-upload git bundle of a working tree for directory sync ends, whatever the result, with the outcome, build_ms and attempts. A built outcome adds bundle_bytes, commit_count, withheld, missing_uploaded_as_deleted and detached; a refused outcome adds reason and sub_reason; a not_served outcome adds not_served_why.v2.1.283 ○gone never read tengu_dir_sync_folder_repo ◇ Folder sync sends per-pass stats so stalled syncs can be diagnosed server-side.never mined ·never mined never read tengu_dir_sync_folder_seed ◇ Folder sync sends per-pass stats so stalled syncs can be diagnosed server-side.never mined ·never mined never read tengu_dir_sync_folder_session ◇ Cloud file sync gains git-bundle and tar-archive modes, but you still sync file by file.never mined ·never mined never read tengu_dir_sync_folder_store_lost ◇ Folder sync sends per-pass stats so stalled syncs can be diagnosed server-side.never mined ·never mined never read tengu_dir_sync_git_config_reread ◇ Directory-sync now detects if git config changed while being read and refuses to trust itnever mined ·never mined never read tengu_dir_sync_git_ended ◇ Git-based directory sync for cloud sessions includes a lock so only one window syncs.never mined ·never mined never read tengu_dir_sync_git_fast_forward ◇ Git-based directory sync for cloud sessions includes a lock so only one window syncs.never mined ·never mined never read
Feedback