feat(plugins): add Mem0 to marketplace

[Himanshu-Sangshetti]

What changed

Adds a curated marketplace entry for Mem0 so Kimi Code CLI users can install it from /plugins. Mem0 gives the agent persistent, cross-session memory of decisions, conventions, and preferences, via the Mem0 MCP server, skills, and auto-capture hooks.

• plugins/marketplace.json: new curated entry
• .changeset/add-mem0-plugin.md: patch changeset

No prior issue, as this is a small marketplace data addition.

Note on source: the plugin lives in a monorepo subdirectory (mem0ai/mem0 at integrations/mem0-plugin), so source is a /tree/main/<subdir> URL rather than a repo root. It installs cleanly as a local path; flagging in case the resolver expects a repo-root manifest, in which case we can point at a dedicated repo.

Checklist

• I have read the CONTRIBUTING document.
• Changeset included.
• No doc update needed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 3997648

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@moonshot-ai/kimi-code	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 39976486cd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Point Mem0 at an installable plugin archive

Selecting this catalog entry cannot install the Mem0 subdirectory: resolveInstallSource treats every segment after /tree/ as the Git ref, so this becomes the ref main/integrations/mem0-plugin, and the GitHub resolver downloads .../zip/main/integrations/mem0-plugin rather than checking out main and extracting that directory. Package the integration as a directly installable archive/repository, or add explicit GitHub-subdirectory support before advertising this source.

Useful? React with 👍 / 👎.

[Himanshu-Sangshetti]

Heads up: the Codex review is correct that the source here points at a monorepo subdir, which the current resolver can't install (source.ts:63 joins the whole tail into the ref). Filed #2945 proposing subdir support and offered to contribute the fix. Marking this draft until the resolver approach is agreed; I'll update the source to the final syntax then.