Compare commits

..

3 Commits

Author SHA1 Message Date
Mgeeeek d233da8245 chore: remove redundant trailing newlines in mem0/__init__.py
Cleans up the placeholder blank lines added in the earlier CI trigger
commit (#5123). Side-effect: this commit touches mem0/** so it satisfies
the ci.yml path filter and unblocks the required build_mem0 /
build_embedchain checks for this docs PR.
2026-05-14 21:32:29 +05:30
Mgeeeek 4d99e5cc41 docs(cli): add Agent Mode + mem0 identify to /platform/cli
PR #5123 added Agent Mode to the CLI but only updated docs/changelog/sdk.mdx;
the main feature page at docs/platform/cli.mdx (which renders at
https://docs.mem0.ai/platform/cli) still documented only the pre-Agent-Mode
commands.

Changes:
- New "Agent Mode — zero-friction signup for AI agents" section placed
  ABOVE regular Authentication, since it's the primary entry point for
  agent users and the page promo positions the CLI as "built for both
  humans and AI agents"
- Subsections: claim flow (`mem0 init --email`), plugin sync behavior
  (`~/.claude/settings.json` + shell rc)
- `mem0 init` flag table extended with --agent, --agent-caller, --source
- New `mem0 identify` subcommand reference (PATCHes the active key's
  agent_caller)

All angle-bracket placeholders inside backticks (e.g. `<your-name>`,
`<memory-id>`) — verified no naked <... JSX traps remain that would
break Mintlify parsing.
2026-05-14 21:27:13 +05:30
Mgeeeek 95a8da31eb fix(docs): escape <5s in CLI v0.2.5 changelog — Mintlify MDX parse error
Mintlify deployment failed after #5123 merged because docs/changelog/sdk.mdx
contained naked `<5s` text. MDX treats `<` as a JSX tag opener, but `5` is
not a valid identifier-start character, so the parser errors:

  "Failed to parse page content at path changelog/sdk.mdx: Unexpected
   character `5` (U+0035) before name, expected a character that can
   start a name, such as a letter, `$`, or `_`"

Replace `in <5s` with `in under 5 seconds`. Other `<...>` patterns in the
entry (e.g. `<name>`, `<email>`, `<their-email>`) are all inside backticks
which Mintlify treats as literal code spans, so they don't trigger the
JSX parser.
2026-05-14 21:23:21 +05:30

Diff Content Not Available