メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | supermemory-logout |
| description | 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. |
| allowed-tools | Bash(node:*) |
Remove saved Supermemory credentials for Codex:
node ~/.codex/supermemory/logout.js
Logout creates an intentional disconnected marker so the automatic recall hook will not reopen browser auth on the next prompt. /supermemory-status should report disconnected after logout. /supermemory-login clears the marker and reconnects.
On Windows, if running the command from Codex, request escalated shell execution immediately instead of trying the sandbox first. The script removes auth files under ~/.codex. Use a narrow approval reason such as:
Run Supermemory logout from the Codex home directory so it can remove saved credentials.
If SUPERMEMORY_CODEX_API_KEY is set in the parent shell, the script cannot unset it. Tell the user to unset that environment variable or restart Codex if the script reports it is still active.
Never print the full API key.
Log in to Supermemory. Use when the user needs to authenticate, set up their API key, or when memory features report a missing 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.