API key integration creates isolated agent space — memories not visible in app #738
Description
Description
I connected Claude Code using an API key after following the instructions on the claude-supermemory README.md. I later discovered the customer app and began using it to observe how memories are created.
It appears that the API key auth path creates an agent-type integration rather than a personal one, which causes several problems with how memories are stored and surfaced.
Problems
Memories periodically disappear from the app
On multiple occasions, all memory contents disappear from the app view. On one occasion, Claude Code itself was also unable to load any memories.
Adding spaces may be a trigger, but I cannot reliably reproduce this yet.
Memories stored in a hidden space
To make memories visible again, I have to list all spaces and manually select a normally-hidden space named Space claudecode_project_<id>. Regular app usage does not surface this space.
Integration not shown as active
My Claude Code integration does not appear as active in the app. The in-app instructions recommend OAuth credentials, while the API docs page directed me to use an API key.
Workaround
Manually selecting the hidden claudecode_project_<id> space restores visibility of existing memories.
Expected behaviour
- API key and OAuth integrations should behave identically from the user's perspective
- Memories should remain visible in the app without manual space selection
- The integration should appear as active
Request
I'd like help migrating to the correct integration type without losing existing memory data.