一键导入
supermemory-login
Log in to Supermemory. Use when the user needs to authenticate, set up their API key, or when memory features report a missing key.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Log in to Supermemory. Use when the user needs to authenticate, set up their API key, or when memory features report a missing key.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | supermemory-login |
| description | Log in to Supermemory. Use when the user needs to authenticate, set up their API key, or when memory features report a missing key. |
| allowed-tools | Bash(node:*) |
Authenticate with Supermemory to enable persistent memory across Codex sessions.
node ~/.codex/supermemory/login.js
On Windows, if running the command from Codex, request escalated shell execution immediately instead of trying the sandbox first. The script lives under ~/.codex, reads/writes auth state there, and may open the browser. Use a narrow approval reason such as:
Run Supermemory login from the Codex home directory so it can read credentials and open the browser auth flow.
This opens a browser window for authentication. Once complete, the API key is saved automatically and memory features activate immediately.
If the browser does not open, the script prints a URL to visit manually.
Never print the full API key. If the script reports that Supermemory is already authenticated, tell the user memory is active and do not ask them to log in again.
Log out of Supermemory in Codex. Use when the user wants to disconnect Supermemory, remove saved credentials, switch accounts, clear auth state, or stop memory from using the current saved API key.
Show Supermemory connection status for Codex. Use when the user asks whether Supermemory is connected, which account or API key is active, memory hook health, or plugin status.
View the user's Supermemory profile (persistent facts and recent context).
Remove outdated or incorrect information from memory. Use when user says something is no longer true, wants to delete a memory, or information has changed.
Save important project knowledge to memory. Use when user wants to preserve architectural decisions, significant bug fixes, design patterns, or important implementation details for future reference.
Search your coding memory. Use when user asks about past work, previous sessions, how something was implemented, what they worked on before, or wants to recall information from earlier sessions.