Repository navigation
π docs: how Hive injects knowledge and memory into agents - #17042
Merged
Merged
Conversation
Answers the 2026-11-05 community-meeting question nobody could answer: which context reaches an agent and from where. Separates the three layers (Hive knowledge primer, CLI conversation, CLI persistent memory), traces the kick-primer path (Primer.PrimeScoped -> primeKnowledge -> # Relevant Knowledge) with its scoping rules and size caps, explains why repo AGENTS.md is injected by the scheduler rather than read natively, lists which per-agent home directories are fleet-shared, and tabulates what survives a kick, /clear, pod restart or a new agent. In-flight memory isolation work (#17031, #17032, #17033, PR #17039) is linked as known gaps rather than described as current behaviour. Signed-off-by: Andrew Anderson <andy@clubanderson.com>
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
Open PR overlap checkBase branch: Conflicts are checked with every PR merged onto the current tip of
|
Contributor
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
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.
Why
At the 2026-11-05 community meeting @kellyaa asked "how does Hive's memory/knowledge injection work today?" and nobody could answer. @gregoryhunt and @Danathar raised the related CLI auto-memory concerns. This is a docs gap; this page closes it.
What
New
src/docs/agent-knowledge-and-memory.md(~215 lines), verified againstv5code:registerKnowledgeStoresβScheduler.primeKnowledge(keywords from the firstmaxIssuesToPrimeissues) βPrimer.PrimeScoped(lifecycle filter,knowledge.agent_scopes, rerank, graph expansion) β# Relevant Knowledge(4096-byte cap) β kick text after/clear;AGENTS.md/CLAUDE.mdis injected by the scheduler and not read natively (CLI cwd is/data/agents/<name>, not a checkout);HOMElayout: which dot-dirsinteractiveHomeBridgeDirsshares fleet-wide and which are per-agent (.copilot,CODEX_HOME,.local,.gitconfig), contributor-container staging, and the fact that nothing in Hive disables or clears CLI memory;/clear/ pod restart / new agent);Linked from
documentation-map.md,operator-reference/README.md(data.claude_sessions_dirrow),agents-md.mdandknowledge-curator.md.Citations are by backticked Go declaration anchor, no
file:line. Docs-only, no changelog fragment needed.