The CLI
npx memcell connect
The CLI is the terminal face of the same memory every other surface reads.
mem works everywhere memcell does. This table is mirrored from the
declarations the CLI's own parser reads — a test fails if they drift.
commands the CLI's own words — memcell --help says the same
| command | what it does |
|---|---|
| memcell login | sign this machine in |
| memcell logout | sign out and forget the session here |
| memcell connect | wire this directory — approves in your browser the first time |
| memcell hook remove | take memcell's hooks out of this directory |
| memcell recall <intent> | what memory serves before you act |
| memcell remember <text> | file one thing this project has established |
| memcell report <statement> <outcome> | what happened when something memory served was acted on |
| memcell ingest <file> | hand a document to this directory's memory |
| memcell import [files…] | bring existing instruction files into memory — bare, it finds them |
| memcell export | carry this space out — one document, no account needed |
| memcell status | who this machine is, and what this directory is linked to |
| memcell reset | forget everything memcell keeps on this machine |
| memcell config get <key> | what a setting is here, and which file said so |
| memcell config set <key> <value> | set it for this project, or for this machine |
| memcell spaces ls | list them |
| memcell spaces new <name> | make one |
| memcell spaces use <slug> | work on this one from now on, everywhere |
| memcell agents ls | list them |
| memcell agents revoke <id> | take one agent's key back |
| memcell memories seed <source> | put a source into the commons, or propose one |
wiring, in one command connect does the whole setup
memcell connect in a project directory prints a code; one tap in your
browser approves it. No account is needed to start — an anonymous session
holds real memory, and signing in later carries it with you. Connect
detects the agents on your machine and wires
each in its own dialect, registers the MCP bridge,
and mints the directory's agent key.
in and out memory is yours to carry — both directions
memcell import run bare finds the instruction files a project already
keeps — CLAUDE.md, AGENTS.md, .cursorrules, .cursor/rules, Copilot
instructions — and hands each through the ingest door,
where it is distilled into statements with provenance rather than stored
as a wall of text. Name files to import exactly those; a JSON export from
another tool goes in the same way when its shape says where the text is.
memcell export carries the space out — as the full JSON document, or as
agents-md, claude-md, or cursorrules with --format, ready to be
read by agents that do not speak memcell. It answers to the directory's
own pair key, so it works with no account, always.
settings project first, then machine — get says which answered
memcell config get <key> answers with the value and which file said
so; set writes to the project or the machine. Settings resolve project
over machine, so a repo can pin what a laptop merely prefers.