Skip to content

Fix V2 runtime ownership across locations - #107

Draft
a-monteiro wants to merge 2 commits into
supermemoryai:mainfrom
a-monteiro:andre/upstream-v2-location-ownership
Draft

a-monteiro wants to merge 2 commits into
supermemoryai:mainfrom
a-monteiro:andre/upstream-v2-location-ownership

Conversation

@a-monteiro

Copy link
Copy Markdown

Keep one V2 runtime owner per location directory instead of replacing the process-wide owner whenever another location loads. Reloading or cleaning up one location no longer unregisters tools and hooks in another; stale cleanup cannot remove a replacement generation.

Regression tests cover two usable locations, same-directory replacement, identity-aware registration disposal, and teardown isolation. All 37 tests, typecheck, and build pass with an isolated test HOME. No version bump or generated artifacts.

Fixes #104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v2 server plugin: only the most recently loaded location keeps its supermemory / supermemory_recall tools

1 participant