Mintlify site published at https://docs.mem0.ai. Every new .mdx page needs three things, or CI fails: docs-llms-txt-check.yml runs on every PR touching docs/*/.mdx and blocks the merge when llms.txt is out of sync. To fix: That scaffolds placeholders under ## Unclassified - needs triage. Then replace each [TODO: ...] tag, rewrite the descriptions as Use when ..., move entries into the correct section, and delete the triage heading once it is empty.
Do not modify any workflow without explicit approval from a maintainer. Publishing credentials are bound to workflow filenames, and the gate workflows decide whether contributions are accepted. Read this file before proposing any change here. ci-gate.yml (CI Gate) is the single entry point. It runs on every PR, detects which packages changed, and calls only the relevant package workflows as reusable workflows (workflow_call). Its final CI Gate job aggregates the results: skipped pipelines pass, failed or cancelled ones fail. It…
Agent and editor integrations. Most packages are self-contained; coding-agent plugins share the code in agent-plugin-core/. Check the table before running anything. pnpm for TypeScript packages except opencode-plugin/ (Bun). mem0-strands/ uses Python/pip/hatch. Never npm or yarn. Run the type check after every TypeScript change: pnpm run typecheck or tsc --noEmit, whichever the package defines. Every integration tells the Mem0 platform which surface it is. Three headers, and the ru
The mem0ai package on PyPI. Memory core plus five pluggable provider categories. Use hatch for environments and dependencies. Do not use pip or conda. Every category follows the same shape: a base.py with the abstract class, one module per provider, config models in configs.py, registration in init.py. Both Memory and MemoryClient expose the same surface: Changing any of these signatures means updating docs/ in the same PR.
The mem0ai package on npm. Hosted client plus self-hosted OSS memory. pnpm only. Never npm, never yarn. Run pnpm run typecheck after every change. The method surface mirrors the Python SDK: add, search, get, getAll, update, delete, deleteAll, history. Changing any public signature means updating docs/ in the same PR. Tag prefix ts-v* triggers ts-sdk-cd.yml, which publishes to npm over OIDC. Bump the version in package.json first.
FastAPI REST server wrapping the Python SDK. Docker only; there is no local non-Docker path. Never commit .env. Credentials for the compose services belong in .env.example as placeholders only.
Claude Code skill definitions published from this repo. Agents fetch them by raw URL, so treat every file here as a public API. Reference skills carry SDK knowledge and are always available: Pipeline skills run on demand and have side effects: mem0-integrate and mem0-test-integration are loosely coupled: they share state only through .mem0-integration/ files, never through conversation context. SKILL.md is loaded in full every time the skill fires, so it is the expensive file. Keep it under 500 lines. Everything…
pytest suite for the mem0/ package. Tests for other packages live with those packages: mem0-ts/ (jest), cli/python/tests/ (pytest), cli/node/ (vitest), and each directory under integrations/.
Agent Skills package for researching any topic across Reddit, X, YouTube, and web. Installable across Claude Code (most common host), Codex, Cursor, GitHub Copilot, Gemini CLI, Grok (xAI), and 50+ other Agent Skills hosts. Python scripts with multi-source search aggregation. Python 3.12+ required. Use uv for the env; the venv lives at .venv/. Agents open most PRs. Follow this so CHANGELOG.md stops conflicting and versions stay lockstep:
Project-specific Rust + Tauri rules: .claude/rules/rust.md. Skills live under .agents/skills/ (/release; .claude/skills/* are symlinks into .agents/skills/, edit the .agents copy only). Exception: the pake skill's real source is plugins/pake/skills/pake/SKILL.md (shipped…
Operating manual for contributors and AI agents touching this repo. Read it before opening a PR. The repo is a curriculum, not a SaaS app. The lessons are the product. Every rule below keeps 523 lessons coherent over time. 523 lessons. 20 phases. Every algorithm built from raw math before a single framework gets imported. You write backprop, the tokenizer, the attention mechanism, and the agent loop by hand in Python, TypeScript, Rust, or Julia. Then you run the same…
CrewAI is a Python based framework for building AI agents and agentic systems. Follow these guidelines when contributing: 1. Follow Python best practices and idiomatic patterns. 2. Maintain existing code structure and organization. 3. Write unit tests for new functionality focusing on behaivor and not implementation. 4. Document public APIs and complex logic. 5. Suggest changes to the docs/ folder when appropriate 6. Follow software principles such as DRY and YAGNI. 7. Keep diffs as minimal as possible. LLMMessage.content is…
**MANDATORY: Read AGENT_GUIDE.md before responding to ANY user message.** Do not act on the user's request until you have read AGENT_GUIDE.md. It contains routing rules that determine your first action…
Version 1.0.0 Black Forest Labs January 2026 Note: This document is for AI agents and LLMs to follow when working with FLUX image generation prompting and workflows. Humans may also…
Version 1.0.0 Engineering January 2026 Note: This document is mainly for agents and LLMs to follow when maintaining, generating, or refactoring React codebases using composition. Humans may also find it…
Version 1.0.0 Vercel Engineering January 2026 Note: This document is mainly for agents and LLMs to follow when maintaining, generating, or refactoring React and Next.js codebases. Humans may also find…
goose is an AI agent framework in Rust with CLI and Electron desktop interfaces. The issue is the source of truth for work intended for an upstream pull request. Track issue status on the Goose Issues board. Maintainer-directed work, urgent security fixes, release automation, and local or exploratory changes do not require a Ready issue. goose is retiring its project-specific MCP server directory in favor of the official MCP Registry and its server.json format. See Discussion #10830 for the decision…
IMPORTANT: The product name "goose" should ALWAYS be written in lowercase "g" in all documentation, blog posts, and any content within this documentation directory. This is a brand guideline that must be strictly followed. This rule applies to: - All markdown files in /docs/ - All blog posts in /blog/ - README files - Configuration files with user-facing text - Any other documentation content When editing or creating content in this documentation directory, always ensure "goose" uses a lowercase "g".
A library for analyzing Kotlin code at the semantic level, providing structured access to symbols, types, and semantic relationships. Entry point: Use analyze() to start an analysis session. See Analysis…
mem0aiAGENTS.md
