Codex Memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_MEMORY_ROOT | No | Memory vault root. Defaults to ~/.codex/memories. | ~/.codex/memories |
| CODEX_MEMORY_SERVICE_ROOT | No | Source checkout root used to find the optional Rust keyword helper. Defaults to the repository root in editable installs. | |
| CODEX_MEMORY_ENABLE_SEMANTIC | No | Set to 1 to enable semantic indexing/search. | |
| CODEX_MEMORY_TRANSCRIPT_ROOTS | No | Extra transcript roots for session and hook tests, separated by the platform path separator. | |
| CODEX_MEMORY_PROJECT_SPECIFIC_TERMS | No | Comma-separated local lint terms used to flag records that should be filed under a concrete project instead of a shared knowledge-base project. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_memoryA | Search local Codex memory with keyword, semantic, or hybrid retrieval. Use comma-separated status values such as "active,risk_pending" to search more than one lifecycle state. Set diagnostics=true to return hits plus per-stage timing fields for retrieval performance troubleshooting. |
| read_memoryA | Read a local memory record by id or path. |
| write_memoryC | Create or update a Markdown memory record. |
| reindex_memoryC | Rebuild local memory indexes. |
| memory_hygieneB | Report local memory hygiene issues such as stale candidates and duplicates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: hygiene, read, reindex, search, and write. No two tools overlap in functionality, ensuring an agent can easily differentiate them.
Four tools follow a consistent verb_noun pattern (read_memory, reindex_memory, search_memory, write_memory), while memory_hygiene uses a noun_noun pattern, causing a minor deviation.
With 5 tools, the server is well-scoped for memory operations. The count feels sufficient without being excessive or insufficient for the domain.
The server covers core read, write, search, and maintenance operations, but lacks a delete tool, which is a notable gap in lifecycle coverage.