RememberStackremember.dev/docs

Remember CLI Reference

RememberStack has two deliberately separate truth layers. Claims are immutable source testimony (“what was asserted, by whom, when”); facts—relations and observations—are the adjudicated worldview (“what the system holds or held true”): supersession-adjudicated, clocked on two time axes (when a fact held in the world, and when the system learned it), evidence-counted per distinct source—repetition is not corroboration—and contradiction-tracked. The fact_claim_evidence association is the auditable bridge between the layers, recording which claims support or contradict each fact. Query claims to inspect testimony; query facts to answer current or historical truth questions, then follow the bridge to see why the system believes or believed the fact.

(Internally these guarantees are decisions D41 and D54.)

The canonical remember CLI (v0.17.0+) ships in the lightweight remember package on PyPI (pip install remember or uvx remember).

It provides a single unified command-line tool for:

  • Agent Onboarding: Interactive setup and diagnostic verification (setup, doctor).
  • Cloud Control Plane: Session management, credit balance, project switching, and team seats (login, whoami, balance, projects, switch, members).
  • Data Plane Operations: Document ingestion, assured retrieval, sandboxed SQL queries, and the MCP server (ingest, operations, query, mcp).
remember --version
# Remember 0.17.0

1. Universal Quickstart & Diagnostics

remember setup

Interactively configures your coding agent harnesses (Cursor, Claude Code, Claude Desktop, Codex, Antigravity) to connect to Remember:

remember setup

Flags:

  • --self-hosted: Connect to a local Docker Compose engine (http://localhost:8000) instead of Remember Cloud.
  • --url <url>: Override the default data plane endpoint.
  • --token <token>: Provide a project data-plane token directly.
  • --dry-run: Preview planned harness configuration files without writing them.

remember doctor

Validates your environment, token health, active project context, backend connectivity, and agent harness registrations:

remember doctor
Remember Diagnostics (CLI v0.17.0)
----------------------------------------
[✓] Configuration: ~/.config/remember/credentials.json (0600)
[✓] Backend connectivity: https://api.remember.dev (200 OK)
[✓] Authentication: Valid session (project: prj_prod_acme)
[✓] MCP Server: uvx remember mcp runnable
[✓] Harnesses configured: Cursor (.cursor/mcp.json), Claude Code
All systems operational.

2. Remember Cloud Control Plane

The control plane commands interact with Remember Cloud (https://api.remember.dev) to manage identity, workspaces, billing, and team collaboration.

Self-Hosted Note: If you run control plane commands with --self-hosted or pointing to a local engine, the CLI outputs an informative notice: "Note: You are connected to a self-hosted engine. Projects, team members, and billing are cloud-managed services on remember.dev."

remember login / remember logout

Authenticates via secure browser-based OAuth device grant:

# Authenticate against Remember Cloud
remember login
 
# Log out and revoke stored tokens
remember logout

Tokens are stored securely in ~/.config/remember/credentials.json with strict directory permissions (0700) and file permissions (0600).

remember whoami

Displays your current authenticated user, email, organization, and active project context:

remember whoami

remember balance (or remember billing)

Checks your available credit balance, active subscription tier, and current monthly spend:

remember balance
Notice: Organization billing and subscription status are managed in the cloud console at https://remember.dev/app/billing.

remember projects list / remember projects create

View and manage isolated workspace projects:

# List available projects in your organization
remember projects list

Project creation and provisioning are managed directly in the cloud console at https://remember.dev/app/projects. Running remember projects create prints direct console guidance and exits.

remember switch <project-id>

Switches your active default project context for subsequent CLI and MCP actions:

remember switch prj_prod_ecommerce

remember members list / remember members invite

Team collaborator management and seat allocations:

Organization member management is performed via the cloud console at https://remember.dev/app/team. Running remember members prints direct console guidance and exits.

3. Data Plane Operations

The data plane commands run identically whether targeting Remember Cloud or a self-hosted engine.

remember ingest <file>

Ingests a file into the content-addressed spine, triggering chunk packing, claim extraction, and bitemporal adjudication:

remember ingest docs/architecture.md

remember operations list / remember operations run

Interacts with Remember's four assured operations:

# List available operations and their schema contracts
remember operations list
 
# Run facts_context
remember operations run facts_context --arg query="Who is the lead architect?"

remember query sql <sql> (Open Query Space)

Executes an AST-sandboxed, read-only SQL query against the memory_v1 view schema.

Open Query Space Parity: Supported on Self-Hosted Engine; planned parity for Remember Cloud under active operator dogfooding.

remember query sql "SELECT fact_id, predicate, fact_label FROM facts_current WHERE predicate = 'works_at' LIMIT 10;"

remember mcp

Launches the Model Context Protocol stdio server for AI coding agents:

remember mcp

remember connectors

Inspect and trigger external document ingestion connectors:

remember connectors list

4. Retired Surfaces

In accordance with Decision D108:

  • remember review: Retired. In early versions, review queues held human triage tasks. In modern Remember, contradiction adjudication is fully autonomous (D3/D43/D107) and runs live in the bitemporal spine. Running remember review prints a helpful migration notice.
  • remember budget: Retired from the primary data-plane surface. Cloud spend and credit balances are managed via remember balance. Self-hosted engine spending is configured via .env provider rate limits.

Resume conversion after adding a route

With engine extras installed and local database access, run:

remember ops resume-no-route --deployment <uuid>

The command reads REMEMBERSTACK_SELFHOST_CONVERSION_ROUTES, validates its adapter names, and releases only live convert rows parked with no_route whose stored MIME now has a converter. Restart workers with the same configuration first. Output is JSON with the released processing IDs; an empty list means nothing matched. Other MIME types stay parked. No original needs re-uploading. A worker still missing a route parks it again without using its attempt allowance. Existing dead-letter rows require the separate remember ops replay operation.