blog: Tuning Recall — Hindsight's Four Retrieval Arms, Explained - #3836
Open
benfrank241 wants to merge 1 commit into
Open
blog: Tuning Recall — Hindsight's Four Retrieval Arms, Explained#3836benfrank241 wants to merge 1 commit into
benfrank241 wants to merge 1 commit into
Conversation
A tuning guide for recall: what each of the four retrieval arms does (semantic, BM25, graph, temporal), the knob and default that controls each, and how to match the pipeline to the shape of a bank. Covers the per-bank toggles including the new enable_text_search (#3819), the recall budget mapping, strategy boosts, recency decay, and the retain-side pairing for plain-retrieval banks. Every default and threshold is taken from configuration.md and the hindsight-api-slim source rather than restated from memory. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Strix Security ReviewNo security issues found. Updated for Reviewed by Strix |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A pillar post on tuning recall: what each of the four retrieval arms does, the knob and default that controls each, and how to match the pipeline to the shape of a bank.
What's in it
0.3, graph seed0.3, temporal0.1, semantic-link0.7, BM25 min score0)enable_text_searchfrom feat(recall): add a per-bank enable_text_search toggle for pure vector recall #3819fixed100/300/1000 vsadaptive), strategy boosts, recency decayretain_extraction_mode: chunks,enable_observations: false) for plain-retrieval banksVerification
Every default, threshold, and env var name is taken from
hindsight-docs/docs/developer/configuration.mdand thehindsight-api-slimsource, not restated from memory. Theenable_text_searchbehavior is checked againstengine/search/retrieval.py:190and the knowledge-page path inengine/memory_engine.py.The post deliberately contains no CLI commands:
set_configinhindsight-cli/src/commands/bank.rsaccepts only the LLM, retain, mission, and disposition params, so none of the four recall toggles are settable via a CLI flag. Configuration is shown through the config API and environment variables only.Files
hindsight-docs/blog/2026-08-27-tuning-recall-retrieval-arms.mdhindsight-docs/static/img/blog/tuning-recall-retrieval-arms.png(1600x900)Noted separately, not fixed here
The "plain-retrieval (RAG) banks" curl example in
configuration.mdstill lists only the three original recall toggles and omitsenable_text_search: false, though that section's premise is making a bank behave like a conventional vector store. #3819 updated the table above it but not the example. Left for its own docs PR.🤖 Generated with Claude Code