An index-backed recall path with detailed timing telemetry sits behind tengu_mill_orange, which falls back to false.
Memory recall has a new branch that selects documents from a search index rather than asking the model to pick, switched off in this build.
- The search entry point takes four extra arguments; when the first is true the new branch uses
searchMemoryFilesWithIndexin place of the model-driven memory selector. - Emits a
memory_recall_selectevent withvia_index,candidate_docs,index_query_term_count,index_hit_count,index_below_floor_count,index_top_score,index_relevance_floor,index_loaded_from_disk,index_took_ms,index_store_held,index_open_wait_msandindex_store_open_ms. - Failure reasons:
index_sweep_incomplete,index_query_failed,below_relevance_floor,no_servable_hits,partially_below_floor,all_filtered. - Gated on
tengu_mill_orange, whose in-source fallback is false; with it off the old selector path runs unchanged.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_mill_orange Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.219: off
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.
Read once, for one account on one subscription tier, against v2.1.219. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: tengu_mill_orange