fix: route Claude session saves to shared repo container#73
fix: route Claude session saves to shared repo container#73MaheshtheDev wants to merge 2 commits into
Conversation
Write session summaries and manual repo memories to repo_* tags while keeping legacy session tag reads for backward-compatible recall.
![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: f97da0dd70
ℹ️ 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".
| const baseUrl = getBaseUrl(cwd, projectConfig); | ||
| const client = new SupermemoryClient(apiKey, undefined, { baseUrl }); | ||
| const containerTag = getContainerTag(cwd); | ||
| const containerTag = getRepoContainerTag(cwd); |
There was a problem hiding this comment.
When repoContainerTag is not configured, getRepoContainerTag() derives the tag from only the repository basename (for example both github.com/acme/api.git and github.com/personal/api.git become repo_api). Routing automatic session summaries through that tag means unrelated repos or forks with the same name under the same Supermemory account will mix recalled context and saved session data; the previous autosave path used a hashed project path and did not have this collision. Consider including the remote owner/full URL or another stable hash in the default repo tag.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
@MaheshtheDev i dont think we need to push cjs files rest lgtm
3 participants
Write session summaries and manual repo memories to repo_* tags while
keeping legacy session tag reads for backward-compatible recall.