Adds a one-time PII warning shown before the first `mem0 agent-rush
add`. Persists acknowledgment in config so we never ask the same
machine twice.
Interactive (TTY):
⚠️ AGENTRUSH memories are PUBLIC — visible to any other player.
Do not include real names, emails, secrets, work content, or PII.
Continue? [y/N]
→ on "y" the timestamp lands in `agent_rush.acknowledged_at`.
→ anything else aborts with no add.
Non-interactive (agent invocation, no TTY): the warning prints to
stderr (visible in the agent transcript so the human notices) and
the add proceeds. Agents can't answer y/N; blocking them would defeat
the entire launch flow. Ack is intentionally not persisted in this
path so a later human run still sees the prompt.
Mirrored across Node + Python CLIs with matching JSON schema:
config.json adds `agent_rush.acknowledged_at: ""` (ISO timestamp).
Mirrors implementation across Node (TypeScript) and Python CLIs.
mem0 whoami:
Prints the agent's default_user_id from local config — the AGENTRUSH
leaderboard identifier. Used by players to cross-verify their row.
mem0 agent-rush <add|search>:
Wraps the platform's /v1/agent-rush/{memories/, memories/search/}
endpoints. Project routing is implicit (server-resolved); no flags.
Pretty-prints platform error codes into actionable hints (e.g.
agentrush_search_first → "Run 3 'mem0 agent-rush search' commands
before adding.").
Adds X-Mem0-Mode: agent-rush header for telemetry. Reuses existing
agent-mode API key from config; surfaces a graceful error if config
is missing or the key was created outside agent-mode.
Platform PR: mem0ai/platform#2804
Mgeeeek