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, focus area or feature.

Works from any folder: the connection is explicit rather than inferred from whichever repo you happen to be standing in. The folder only supplies a default.

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 famnly -a Growth # bind to a focus area, no feature
  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>] [--focus-area <focus-area>] [--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 of the instance this terminal is bound to. Ctrl-C to exit.

usage
rememd watch [--instance <instance>]

Homes: boxes and this Mac

Registering a box you run, joining one somebody else runs, seeing who you are on each, and moving a workspace between homes.

rememd instances

List the homes this machine knows: disks, boxes, credentials, and who you are on each.

usage
rememd instances <subcommand>

rememd add-instance

Register a rememd backend you run, with its address and admin token.

Run on the machine whose app and terminals will use the box - registering is something a client does, so the box's own copy of rememd is never involved. Keep the token out of shell history by piping it in:

ssh box 'grep ^REMEMD_ADMIN_TOKEN= backend/.env | cut -d= -f2-' \
    | rememd add-instance --server https://api.example.com --token-stdin
pbpaste | rememd add-instance --server https://api.example.com --token-stdin

Or export REMEMD_ADMIN_TOKEN and run it with no token flag; in a terminal with neither it asks, without echoing. The token is REMEMD_ADMIN_TOKEN from the box's backend/.env. Nothing already on this machine moves: registering a box adds a place workspaces can live.

usage
rememd add-instance --server <server> [--token <token>] [--token-stdin] [--name <name>]

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 instance this terminal is bound to - or on every instance, when it is not.

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> ...] [--to <to>] [--from <from>]

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] [--from <from>]

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. Run the demo app (make demo-app, then open rememd-demo.app) and address it by setting the same variable its bundle pins:

REMEMD_MODE=demo rememd take list
  REMEMD_MODE=demo rememd take run panel
  REMEMD_MODE=demo rememd take run tasks --speed 0.5      # half speed, for a
closer look
  REMEMD_MODE=demo rememd take run session --dry-run      # print the beats,
send nothing

The demo world is three homes - this Mac, a personal box and a team box - with six workspaces between them. Takes perform on Northwind, which lives on the team box.

usage
rememd take <subcommand>

Everything else

Commands the binary reports that this page has not sorted into a group yet.

rememd archive

Archive closed sessions' events out of the hot index.

Sessions logged and quiet for 7+ days have their low-signal event bodies moved to per-session archive documents; after 120 days the rows themselves follow. Logs, notes, plans, diagrams and reported issues never leave the index. Timelines still render in full - readers restore archived rows from the documents.

rememd archive --dry-run          # say what would move, move nothing
  rememd archive                    # all workspaces
  rememd archive --workspace flur   # one workspace, by name substring
usage
rememd archive [--dry-run] [--workspace <workspace>]