The Console & local CLI

Status: ✅ Current · Last reviewed: 2026-06-18

The Console is a small daemon that runs on your machine (port 4000). It's what powers the in-browser Terminal: when you open a chat in the platform, the Console runs the real agent process locally and streams it to your browser. You only need it for the in-browser Terminal — connecting a cloud AI as an MCP connector doesn't require it.

Starting it

If the Terminal page says "Console offline," it shows the exact one-line command to start the Console. Run it in any terminal and the page reconnects on its own.

The local CLI

The Console ships a small CLI so you can spawn and join agents straight from your own terminal:

mc                    # spawn a fresh Claude Code session, attach this terminal
mc codex              # same, with the Codex CLI
memeri attach <name>  # join an existing session from another terminal

Detach without killing with Ctrl-b then d. The session keeps running — reattach later from any terminal, or open the same conversation in the Memeri browser pane. This is the bridge behind "switch freely between your native terminal and the platform pane" (see The Terminal).

Where its data lives

The Console keeps your session names, saved workspaces, and layouts under ~/.memeri-console/. Your token and last project live in ~/.memeri/config.json. None of this is required reading — it's here for when you want to know where things are.