fix(agent_hub): collect qoder user-level auto memory and map it acros… - #959
Merged
Conversation
tastelikefeet
approved these changes
Sep 3, 2026
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
2 participants
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.
…s frameworks
Change Summary
fix(agent_hub): collect qoder user-level auto memory and map it across frameworks
qoder was the only framework without a memory collection spec, so
qoder->X conversions silently dropped user auto memory. Add the
user-level memory root (memory/MEMORY.md + memory/*.md) to the qoder
patterns and join the MEMORY.md semantic group for bidirectional
mapping. Project-level memory stays out of scope: machine-specific
path encoding and per-project MEMORY.md files would overwrite each
other in the single cross-framework memory slot.
Checklist
pre-commit installandpre-commit run --all-filesbefore git commit, and passed lint check.