Claude warms the memory recall index at startup so your first recall is faster.
What's wrong with this entry?
A startup task warms the recall and memory index in the background so the first recall does not pay the indexing cost.
- Invoked once from both boot paths.
- Bails out if the invocation looks like a resume (
--resume,--continue,--from-pr, or a short flag containing c or r), or if index exclusions are already loaded. - Only proceeds when auto-memory, memory recall and index recall are all enabled, and waits for the org-memory decision to settle when multi-store sync is in play.
- Failures are swallowed with a debug line rather than surfaced.
maybePrewarmRecallIndex, recall prewarm skipped:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
--continueand--resumefailures now say what went wrongBoth mention resume continue
-
v2.1.232
--session-id now works with --continue/--resume under an SDK URL
Both mention resume continue
-
v2.1.229
remote-control --continue is documented as reattaching, not resuming
Both mention continue