Ai

Mem0 CLI v0.2.7 Adds Agent Rush Commands and PII Safety

Mem0 CLI v0.2.7 Adds Agent Rush Commands and PII Safety

Mem0 just dropped CLI version 0.2.7, and it's not your average bug-fix release. This update brings two new commands and a privacy guardrail that AI developers—especially those jumping into the AGENTRUSH game—should care about. The headline? You can now check your agent's identity and interact with the leaderboard without leaving the terminal. But there's more beneath the surface.

What Changed

First, mem0 whoami. Run it, and it prints the active agent's default_user_id—the identifier used on the AGENTRUSH leaderboard. No network calls, just local config. Simple, but saves a trip to the docs.

Second, the big one: mem0 agent-rush <add | search>. This new subcommand group wraps the platform's /v1/agent-rush/ endpoints for the 7-day AGENTRUSH competition. Project routing is implicit—no flags exposed. So you can push or query agent data straight from the CLI. It's a developer-friendly move that treats the game like an API-first experience.

Finally, there's a PII safety prompt. On first interactive use of mem0 agent-rush add, you'll see a warning. Acknowledge it, and the choice is stored in ~/.mem0/config.json under agent_rush.acknowledged. It's a small but critical addition—data privacy is a hot topic, and this puts a consent step right in the workflow.

Why It Matters

These changes might seem minor, but they shift how developers interact with the Mem0 platform. The whoami command is a time-saver for multi-agent setups. The agent-rush commands lower the barrier to participating in the AGENTRUSH game—no more fumbling with curl or external dashboards.

But the real story is the PII prompt. It signals that the team takes data ethics seriously, especially in a competitive environment like AGENTRUSH where agent behavior is public. For anyone building agents that might handle personal data, this is a welcome—and potentially trendsetting—design choice. It's the kind of friction that prevents headaches later.

Of course, not everyone will love the extra click. But given the regulatory climate, I'd argue it's better to be safe than sorry. Mem0 is betting that developers appreciate a nudge toward responsible AI—and I think they're right.

Official Source: https://github.com/mem0ai/mem0/releases/tag/cli-v0.2.7