fix: MCP proxy uses the repo space instead of activeSpace - #124
Conversation
Hosted MCP defaults a missing containerTag to the user's durable activeSpace, so plugin search/save could miss the repo container the hooks already write to. Inject the repo tag on space-scoped tool calls unless one is already set.
Proxy injection means omitting containerTag no longer hits activeSpace. Tell the model search_memory is already scoped to this project, and to pass containerTag only when searching somewhere else.
CI does not bump the marketplace version. Ship the repo-space MCP routing fix as 0.1.7 so plugin update notices fire.
This reverts commit 490b27a.
Same mechanism as codex-supermemory: patch-bump on main, skip the follow-up chore(release) commit. Syncs package.json, plugin.json, and latest.json. No npm publish — this is a Claude Code marketplace plugin.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ae2bac0096
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| git commit -m "chore(release): ${VERSION}" | ||
|
|
||
| - name: Push version bump | ||
| run: git push origin HEAD:main |
There was a problem hiding this comment.
When multiple commits reach main before their release runs finish, each run checks out its own event SHA and creates a different bump commit; after one run or a later merge advances main, this unconditional push can be rejected as non-fast-forward. Git permits ordinary branch updates only when the new tip descends from the remote tip (git-push documentation), so the workflow can fail and omit the promised per-merge version bump. Cancel stale runs or fetch/rebase and regenerate the bump before retrying the push.
Useful? React with 👍 / 👎.
2 participants
Plugin hooks already read and write
repo_<name>__<hash>, but the MCP proxy was a pass-through tomcp.supermemory.ai. Hosted MCP treats a missingcontainerTagas the user's durableactiveSpace(shared across every MCP client), sosearch_memory/add_memoryfrom Claude Code could hit a completely different space than the one capture and recall use.The proxy now injects
getContainerTag(cwd)on space-scopedtools/callrequests whencontainerTagis omitted. An explicit tag is left alone, andset-active-tag/whoAmI/tools/listare not rewritten, so this does not clobber the user's global active space.Recall advertising is updated to match:
search_memorydefaults to this project's container; passcontainerTagonly to search somewhere else. That inverts the omit-means-activeSpace bullet in #125.On merge to main, a Release workflow patch-bumps
package.json,plugin.json, andlatest.json(same mechanism as Codex, without npm publish). The PR itself stays on 0.1.6 so merge becomes 0.1.7.Tests cover injection, explicit overrides, unrelated tools, and the new recall copy.