{"version":"2.1.278","anchor":"new-gate-tengu-quiet-lantern-controls-arbiter-local-fallback","canonical_anchor":"new-gate-tengu-quiet-lantern-controls-arbiter-local-fallback","heading":"New gate tengu_quiet_lantern controls arbiter local-fallback triggers","tier":"soon","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278\/e\/new-gate-tengu-quiet-lantern-controls-arbiter-local-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278","markdown":"### New gate tengu_quiet_lantern controls arbiter local-fallback triggers\n\nA new gate, tengu_quiet_lantern, controls whether the server classifier falls back to local when unsupported\n\n**What**\n\nA new feature flag, `tengu_quiet_lantern`, has been added to control whether auto mode's server-side (\"arbiter\") classifier falls back to local classification specifically when the server returns no result or reports the feature as unsupported.\n\n**Why**\n\nThis lets the server-classifier fallback behavior be turned on or off independently for different accounts, rather than being hard-coded into every install. Nothing has been read yet about which accounts have it on.\n\n- Flag `tengu_quiet_lantern`: Not enough to say (read for one account on one subscription tier against v2.1.278; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Auto Mode\n- Names: `tengu_quiet_lantern`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}