Mem0 CLI Configuration

Everything about configuring the mem0 CLI: config file format, environment variables, the init wizard, and precedence rules.

Config File Location

The restricted permissions ensure API keys are not world-readable.

Config File Schema

{
  "version": 1,
  "defaults": {
    "user_id": "",
    "agent_id": "",
    "app_id": "",
    "run_id": ""
  },
  "platform": {
    "api_key": "",
    "base_url": "https://api.mem0.ai"
  }
}

Field Reference

mem0 init Wizard

The init command provides two authentication flows:

API Key Flow (default)

# Fully interactive:
mem0 init

# Fully non-interactive:
mem0 init --api-key m0-xxx --user-id alice

Interactive mode steps:

1. Displays the mem0 banner.
2. Checks for existing config. If found with an API key, asks for confirmation to overwrite.
3. Prompts for API key (input masked with * characters; supports backspace and Ctrl+U to clear).
4. Prompts for default user ID (default value: mem0-cli).
5. Validates the connection by calling the status endpoint.
6. Saves config to ~/.mem0/config.json with 0600 permissions.
7. Prints success message.

Non-interactive mode: When both --api-key and --user-id are provided, skips all prompts and saves directly. When running in a non-TTY without both flags, prints an error:

Non-interactive terminal detected and missing required flags.
Usage: mem0 init --api-key <key> --user-id <id>

Email Login Flow

# Interactive (prompts for code):
mem0 init --email [email protected]

# Fully non-interactive:
mem0 init --email [email protected] --code 482901

Steps:

1. Sends a 6-digit verification code to the email via POST /api/v1/auth/email_code/.
2. If --code is provided, verifies immediately. Otherwise prompts for the code.
3. On success: receives API key, org_id, and project_id from the server.
4. Saves to config. Creates a new account if the email is not registered.

Cannot be combined with --api-key.

Force Overwrite

If ~/.mem0/config.json already exists with an API key, mem0 init warns and asks for confirmation. Use --force to skip:

mem0 init --api-key m0-new-key --user-id alice --force

mem0 config Subcommands

mem0 config show

Displays the current configuration as a formatted table (text mode) or JSON envelope (json mode). API keys are always redacted.

mem0 config show
mem0 config show -o json

mem0 config get <key>

Reads a single configuration value. The key uses dotted notation.

mem0 config get platform.api_key     # prints: m0-x...xxxx (redacted)
mem0 config get defaults.user_id     # prints: alice

Valid keys:

• platform.api_key
• platform.base_url
• defaults.user_id
• defaults.agent_id
• defaults.app_id
• defaults.run_id

Unknown keys print an error message.

mem0 config set <key> <value>

Sets a configuration value and saves the config file.

mem0 config set defaults.user_id alice
mem0 config set platform.base_url https://api.mem0.ai

Type coercion:

• Boolean fields accept true, 1, yes (case-insensitive) as true. Anything else is false.
• Integer fields are parsed with parseInt.
• String fields are stored as-is.

mem0 config clear

Removes the config file (~/.mem0/config.json).

mem0 config clear

Environment Variables

Environment variables override config file values but are overridden by CLI flags.

Precedence

Configuration values are resolved in this order (highest priority first):

1. CLI flags        --api-key, --user-id, --base-url, etc.
2. Environment vars MEM0_API_KEY, MEM0_USER_ID, etc.
3. Config file      ~/.mem0/config.json
4. Defaults         Hardcoded defaults (empty strings, false, https://api.mem0.ai)

Example: If your config file has user_id: "bob", the env var MEM0_USER_ID=charlie is set, and you pass --user-id alice on the command line, the effective user_id is alice.

API Key Redaction Rules

Whenever an API key is displayed (in config show, config get, status output, etc.), it is redacted:

Examples:

• "" -> (not set)
• "m0-abc" -> m0***
• "m0-abcdefghijklmnop" -> m0-a...mnop

The redaction function is named redact_key (Python) / redactKey (Node).

Dotted Key Map

The config get and config set commands use dotted key paths. Here is the full mapping: