fix: keep Agora memory provenance outside model context - #44
Merged
Conversation
zhuqingyv
marked this pull request as ready for review
July 13, 2026 15:52
zhuqingyv
added a commit
that referenced
this pull request
Jul 15, 2026
* feat: redesign Agora memory control plane * fix: include postinstall in npm package * feat: integrate Agora Memory v2 * fix: require notarized Agora release evidence * fix: display the actual MA package version * fix: make startup responsive and file reads provable * fix: gate Agora lock on standalone release evidence * fix: keep Agora memory provenance outside model context (#44) * fix: keep Agora memory provenance outside model context * docs: keep memory management in host control plane * fix: prevent hidden provenance speculation (#45) * fix: render Agora generation as indeterminate progress * feat: expose MA as an ACP runtime * build: add a packageable MA ACP entry * fix: isolate ACP host configuration * fix: harden hosted MA isolation
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
1 participant
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 changed
agora_memory_*management tools from the model-visible tool list./memorycommands, UI console, and metadata-driven mounting intact.chat_completerequest.Root cause
The host exposed MemoryPatch terminology and management tool schemas to every model request. Under leading questions, the model used that leaked vocabulary to invent a false explanation that memory facts were injected into its prompt.
User impact
Ordinary chat now receives native MemoryPatch behavior without knowing that a patch is mounted. Memory operations remain explicit host control-plane actions.
Validation
npm run buildnpm test: 409 tests, 401 passed, 8 explicit skips, 0 failedagora_memory_*terms.