Lists all projects with stored memories for the current user, showing memory counts and last activity dates. Use when checking which projects have memories, comparing memory distribution across repos, or finding a specific project scope.
| name | list-projects |
| description | Lists all projects with stored memories for the current user, showing memory counts and last activity dates. Use when checking which projects have memories, comparing memory distribution across repos, or finding a specific project scope. |
Show all known project scopes for the current user.
There is no dedicated "list projects" API endpoint. Discover projects by fetching the user's memories across all scopes.
Important: A filter with only user_id triggers implicit null scoping — it
excludes memories that have a non-null app_id. Run two queries and merge:
get_memories with filters={"AND": [{"user_id": "<active_user_id>"}]}, page_size=200
— catches memories without app_idget_memories with filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": {"exists": true}}]}, page_size=200
— catches memories with any app_idRun both calls in parallel. Merge results, deduplicate by memory id.
If either response indicates more pages, paginate (up to 1000 total).
For each memory, determine project by:
app_id field (preferred)metadata.project_id (legacy memories)metadata.project (oldest format)"(unscoped)" if none foundGroup by resolved project name. For each project, count:
created_at datemetadata.type values by frequency## mem0 projects
<app_id_1> <count> memories (last: <date>) ← current
<app_id_2> <count> memories (last: <date>)
<N> projects, <M> total memories
Mark current project with ← current. Sort by memory count descending.
If zero memories found:
No projects found. Run /mem0:onboard to get started.
IMPORTANT: Do NOT use markdown in your output. OpenCode TUI renders text verbatim — markdown like bold, ## headers, and | table | syntax appears as raw characters. Use plain text with indentation for structure. Use dashes for lists. Use spaces to align columns instead of markdown tables.
Sets up mem0 for a new project including API key configuration, MCP authentication, project file import, and coding categories. Use on first run in a new project, when API key needs updating, or to re-run initial setup after configuration changes.
Overrides the auto-detected project scope to read and write memories under a different project ID, or enables global search to access all memories across all users and projects. Use when working across multiple projects, accessing memories from another repo, enabling team-wide memory access, or when auto-detection resolves to the wrong project.
Sets up mem0 for a new project including API key configuration, MCP authentication, project file import, and coding categories. Use on first run in a new project, when API key needs updating, or to re-run initial setup after configuration changes.
Overrides the auto-detected project scope to read and write memories under a different project ID, or enables global search to access all memories across all users and projects. Use when working across multiple projects, accessing memories from another repo, enabling team-wide memory access, or when auto-detection resolves to the wrong project.
Mem0 SDK reference covering Python and TypeScript APIs, memory client methods, configuration, and framework integrations. Use when writing code that calls mem0 APIs, configuring memory providers, or integrating mem0 into an application.
Searches and injects relevant memories into context before starting work on a task. Use when beginning a new task, switching context, or when project history, past decisions, or coding conventions need to be loaded.
