docs(memory): correct memory auto-injection drift (closes #108)#122
Open
umi-appcoder[bot] wants to merge 1 commit into
Open
docs(memory): correct memory auto-injection drift (closes #108)#122umi-appcoder[bot] wants to merge 1 commit into
umi-appcoder[bot] wants to merge 1 commit into
Conversation
The docs claimed Claude memory is auto-injected into every prompt via a UserPromptSubmit hook. That's not the actual behavior — it's a deliberate design choice that the docs never caught up with: - seed_claude_config.py strips the UserPromptSubmit memory hook from ~/.claude/settings.json on every boot (memory is on-demand via MCP). - Task-creation pre-injection is gated behind KC_MEMORY_PREINJECT (server.py), which is OFF by default. So memory is on-demand via the MCP tools by default; pre-injection is opt-in; the per-prompt hook ships but is unwired. Update the docs to match reality (Option B in #108 — no runtime change, the behavior is intentional): - docs/persistent-memory.md: rewrite "Auto-injection (two layers)" -> "How Claude reads memory"; fix the file-map rows + troubleshooting row; Roadmap line. - docs/in-app/memory-concepts.md + getting-started.md: lead with on-demand MCP lookup; pre-injection as opt-in. - README.md: same correction. Docs-only. Closes #108 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Fixes the documentation drift in #108. The docs claimed Claude memory is auto-injected into every prompt via a
UserPromptSubmithook; that is not the actual behavior. Docs-only — PR 4 of the reliability-hardening series (good-first).The reality (deliberate, not a bug)
seed_claude_config.pystrips theUserPromptSubmitmemory hook from~/.claude/settings.jsonon every boot — memory is on-demand via the MCP tools.KC_MEMORY_PREINJECT(server.py), which is off by default.Both are intentional (the code comments say so), so the right fix is Option B from the issue — make the docs match the behavior, no runtime change.
Changes
Docs-only; no code touched.
Closes #108
🤖 Generated with Claude Code