CLI reference

Every subcommand, read out of the binary rather than transcribed from it. Run rememd help <subcommand> for the full flag list — this page carries the same text.

Installing it

The Mac app installs the CLI for you on first launch, and offers to update it when the app is replaced. If you want to do it yourself from a source checkout:

cd Prompto && make install

It stages the binary and renames it into place rather than copying over the live one — overwriting a Mach-O under a running process is a SIGKILL, and every agent holding an MCP server would go with it. A running MCP server also keeps the binary it started with, so new behaviour reaches an agent only in a fresh session.

Binding a terminal

The connection is what decides which product and feature every tool call lands on. It is per-terminal and explicit — the folder only supplies a default.

rememd connect

Connect this terminal to a rememd product/feature.

Works from any folder — rememd is memory, not a repo tool. The folder only supplies a default; the connection itself is explicit.

rememd connect                  # pick everything in the menu bar
  rememd connect famnly           # pick the feature in the menu bar
  rememd connect famnly -f "Track usage"
  rememd connect --product-only famnly
  rememd disconnect

Then start your agent as usual. To connect an agent that is already running, just run this in another pane — it will pick the change up on its next rememd tool call.

usage
rememd connect [<product>] [--feature <feature>] [--workspace <workspace>] [--product-only]

rememd disconnect

Disconnect this folder and log its session.

Only needed when you want to stop recording while continuing to work. Quitting your agent does NOT require this — an unlogged session stays open and resumes next time you connect.

usage
rememd disconnect

rememd where

Show what 'current project' resolves to from your cwd.

usage
rememd where

Link a local folder as the context boundary for a focus area or feature (per-user, not synced).

The linked folder is a *container*. Any cwd beneath it — git repo or not — inherits that focus area's context. Mapping lives in ~/.recall/repo-map.json and is never shared with teammates.

Examples:
  rememd link focus-area "Development" ~/work/famnly
  rememd link feature "1.3 CI/CD" ~/work/famnly-cicd-worktree
  rememd link show
  rememd link unlink focus-area "Development"
usage
rememd link <subcommand>

Capturing as you work

The writes you make from a shell rather than through an agent.

rememd note

Capture a quick note for the current project.

"Current project" is inferred from your cwd — rememd finds the git repo root, looks it up in ~/.recall/repo-map.json, and uses the linked focus area's product. Run `rememd where` to see what resolves.

If your cwd isn't linked, run: rememd link focus-area <name> <path>

usage
rememd note [<words> ...]

rememd log

Save a session log for the current repo.

usage
rememd log [--title <title>]

rememd task

Claim, release, or inspect tasks.

usage
rememd task <subcommand>

Reading back

What the next session starts from.

rememd resume

Print context from the most recent session for this project.

usage
rememd resume [<project-name>]

rememd ls

List workspaces, products, focus areas, features, or tasks.

usage
rememd ls <subcommand>

rememd prd

Show or edit a feature PRD.

usage
rememd prd <subcommand>

rememd watch

Tail the live event stream (remote mode). Ctrl-C to exit.

usage
rememd watch

Joining and moving data

Joining a backend someone else runs, and moving a workspace between homes.

rememd join

Join a rememd backend using an invite.

usage
rememd join <invite> [--server <server>] [--name <name>] [--email <email>]

rememd me

Print who you are on the remote backend.

usage
rememd me

rememd migrate-to-remote

Upload local ~/Recall/ data to the configured rememd backend. Preserves UUIDs.

usage
rememd migrate-to-remote [--dry-run] [--workspace <workspace> ...]

rememd migrate-to-local

Download everything from the rememd backend into ~/Recall/. Preserves UUIDs.

usage
rememd migrate-to-local [--dry-run] [--workspace <workspace> ...] [--into <into>] [--force] [--switch-mode]

Maintenance

Diagnosing an install, and the app itself.

rememd doctor

Diagnose (and optionally repair) stale rememd setup on this machine.

Checks MCP registration, legacy bootstrap files, and orphaned connections.

rememd doctor              # report only
  rememd doctor --fix        # quarantine leftovers and repair registration
  rememd doctor --path ~/dev # limit the file scan

Nothing is deleted. Files are moved to ~/.recall/doctor-quarantine/<timestamp>/ with their original paths preserved, so a bad call can be undone by moving them back.

usage
rememd doctor [--fix] [--path <path>] [--depth <depth>]

rememd open

Open the rememd app (and scope it to the current repo if applicable).

usage
rememd open

rememd version

Print this binary's build id, size and path.

usage
rememd version

rememd take

Drive the app through a scripted sequence, for screen recordings.

Demo mode only. Switch first:

rememd mode set demo      # then relaunch the app

Then:

rememd take list
  rememd take run panel
  rememd take run tasks --speed 0.5      # half speed, for a closer look
  rememd take run session --dry-run      # print the beats, send nothing
usage
rememd take <subcommand>