BotCreds Agent Memory gives your AI agents a persistent, structured memory store accessible via WordPress REST API and MCP (Model Context Protocol).

Two modes of operation:

KV Mode (default) — Simple key-value store with tags, expiry, and text search. No external dependencies. Works out of the box.
Vector Mode — Add an OpenAI API key to unlock semantic search powered by embeddings. Entries are embedded in the background and searched by meaning alongside keyword matches. Pending embeddings remain searchable by exact text.

Conversation archive and sync (3.1):

Save explicitly selected original conversation text outside a chat tool, with resumable uploads, session records, artifact references and compaction checkpoints. Retrieve original passages and search archive text within an explicitly enrolled scope. The included reference client reads operator-reviewed JSONL files; it is not an automatic OpenClaw or Claude Code collector.

Manually delete a conversation and its managed archive/checkpoint/session/artifact records, with permanent deletion markers that prevent stale clients from re-uploading it. No automatic age-based forgetting is enabled. Independent curated KV memory, external files and backups are not deleted by archive deletion. In 3.2, managed derived memories tied to deleted sources are purged as described below.

Archive access is separate from shared-memory grants: a host administrator must explicitly enroll each scope/user, including administrators, using wp agent-memory archive-scope project/name USER_ID. Server sync operations require InnoDB tables. Checkpoints verify submitted archive ranges, not completeness of native client capture. No original conversations are captured or uploaded automatically.

Suggestions and evidence-backed memory (3.2):

Agent Memory Suggestions provides original-source selection, optional WordPress AI Client/Connectors generation, an evidence-linked review inbox, immutable revisions, and explicit application of approved facts/decisions to current shared memory. Approval alone does not publish a memory. Generated Skill files are never installed or executed.

Archive scopes require explicit host enrollment, separate from curated-memory grants, including for administrators. Native generation requires compatible WordPress AI Client/Connectors APIs and a configured provider; basic storage/search and external proposal clients do not. Applying a suggestion publishes into the shared curated store, whose readers may differ from archive participants. Source deletion also purges managed derived memory. Automatic conversation capture is not included.

Key features:

REST API with full CRUD (create, read, update, delete)
MCP endpoint for AI agent tool integration
Namespace-based access control per WordPress user
Automatic embedding generation via WP-Cron
Bulk backfill for existing entries
Expiry support for temporary memories
Tag-based filtering and organization
WordPress Application Password authentication

Built for AI agents, by AI agents.

Use this plugin for one human and their agents, or for trusted family/group participants who deliberately share and collaborate on memory. It is not a private-vault hosting service for mutually untrusted users. Memory is API-first; only administrators can browse raw memory in wp-admin. Full and prefix grants include reading, modifying, overwriting, deleting and linking shared entries.

Codex Integration

BotCreds Agent Memory ships official tool adapters for OpenAI Codex in assets/codex/.

Quick start:

Set env vars: BOTCREDS_MEMORY_URL (your WP site) and BOTCREDS_MEMORY_KEY (username:app_password)
Copy assets/codex/AGENTS.md content into your project’s AGENTS.md
Import tools in your Codex task: import tools from './assets/codex/memory-tools.js' (JS) or add memory-tools.py to your repo

Full docs: https://botcreds.com/agent-memory/

External services

This plugin optionally connects to the OpenAI API to generate vector embeddings for semantic search.

Service: OpenAI Embeddings API (https://api.openai.com/v1/embeddings)
When it is used: Only when an OpenAI API key is configured in the plugin settings. Without a key, the plugin operates in KV-only mode and makes no external requests.
What is sent: The text content of memory entries you explicitly write or update.
OpenAI Terms of Use: https://openai.com/policies/terms-of-use
OpenAI Privacy Policy: https://openai.com/policies/privacy-policy