agentmemory-codex-windows
Provides memory and context persistence for OpenAI Codex, capturing user prompts and assistant responses to preserve useful context across coding tasks.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agentmemory-codex-windowsrecall what we discussed about the deployment issue last week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AgentMemory for Codex on Windows
Independent, Windows-native AgentMemory downstream for OpenAI Codex Desktop and Codex CLI.
This is an independent source-only Technical Preview. It is based onAgentMemory v0.9.29, but it is
not the official upstream repository, an @agentmemory/* npm release, or a
promise of upstream support. Do not use an upstream npx command or the
compatibility plugin manifests as a substitute for the Windows build and
installer described here.
Development note: this downstream is AI-generated and user-tested; read the full disclosure.
What this preview does
AgentMemory preserves useful context across Codex tasks while keeping the official AgentMemory memory, lesson, graph, audit, and provenance stores as the only canonical stores.
Captures normal main-agent user prompts and final assistant responses through four managed Codex hooks:
SessionStart,UserPromptSubmit,Stop, andSessionEnd.Excludes ambient UI, title/fork traffic, known internal host prompts, and subagent traffic from durable capture.
Keeps writes, deletion, curation, and provenance exact-project scoped.
Supports bounded, source-labelled federated recall across projects without allowing wildcard writes.
Can use a credential-free, loopback-only local Qwen worker for typed graph extraction. Every other AgentMemory LLM feature receives the noop provider; external fallbacks remain disabled.
Uses an authenticated loopback MCP endpoint for Codex and retains a packaged stdio launcher only as a compatibility path.
The upstream-compatible source surface contains 56 MCP tools. Its MCP surface is 56 tools, 6 resources, and 3 prompts; it also has 133 endpoints on port 3111, 12 portable hooks, and 17 skills. The supported Windows profile intentionally activates only the four managed hooks listed above.
Related MCP server: remem
Version identities
Identity | Value | Meaning |
Downstream release |
| Public version and source tag |
AgentMemory compatibility |
| CLI, MCP, package, API, export, and installed-runtime compatibility |
Qualification revision |
| Internal build provenance, not a public version line |
iii engine |
| Pinned native runtime input, verified by SHA-256 during the build |
The exact upstream tag, commit, tree, and pristine package hash are recorded in
upstream-source.json.
Requirements
Windows with PowerShell 5.1 or newer; this preview is qualified on Windows 11
Node.js 20 or newer
pnpm
11.19.0through the repository's pinned package-manager declarationThe official iii engine
0.11.2Windows executable whose SHA-256 matchespackaging/windows-codex/config/third-party-inputs.json
No prebuilt or signed installer is attached to the first source preview.
Build and evaluate from source
Clone the repository on Windows, then run the release builder from PowerShell. The output directory must not already exist.
git clone https://github.com/M-T-D-N/agentmemory-codex-windows.git
Set-Location agentmemory-codex-windows
& .\packaging\windows-codex\Build-WindowsCodex.ps1 `
-OutputDirectory D:\staging\agentmemory-codex `
-IiiEnginePath D:\inputs\iii-0.11.2.exeThe normal builder verifies the pinned native input, restores the frozen lock, checks generated skills, type-checks, builds, runs the package and Codex adapter tests, creates a production dependency tree, and writes a complete immutable file manifest.
The installer is dry-run by default. It validates release hashes, ownership,
paths, and the existing installation before changing anything. Review the exact
build, dry-run, cutover, rollback, retention, and authentication contract in
packaging/windows-codex/README.md before
using -Execute.
The Windows installer is designed for an owned, managed AgentMemoryCodex
service layout. Do not point it at an unrelated directory or treat build
output as user data. Canonicaldata, secrets, logs, task identity, and
rollback state have independent lifecycles.
Privacy and security boundaries
MCP and service traffic stay on authenticated loopback endpoints in the supported profile.
The optional Qwen provider accepts only credential-free loopback HTTP and is capability-scoped to graph extraction.
The source tree contains no memory database, session transcript, user export, API key, generated installer, or private development history.
Security reports should use GitHub's private vulnerability reporting flow; see
SECURITY.md.
Repository map
Path | Purpose |
| AgentMemory compatibility source |
| Supported Windows/Codex adapter, builder, installer, and tests |
| Upstream-compatible plugin assets bundled into the source build; not the supported installation path |
| Unit and security regression tests |
| Upstream-derived harnesses and historical reference results; not Windows preview qualification |
| Compatibility integrations; not separately supported downstream products |
| Exact upstream provenance |
The upstream marketing website, cloud deployment examples, other upstream language copies, generated build output, and private monorepo history are intentionally outside the first public repository snapshot. Historical benchmark material is retained only for reproducibility and is explicitly labelled as upstream reference; no benchmark number in those directories is a claim for this downstream preview.
Development checks
pnpm install --frozen-lockfile
pnpm run skills:check
pnpm run typecheck
pnpm run build
pnpm test
node packaging/windows-codex/tests/codex-turn.test.mjsThe repository is marked private in package manifests to prevent accidental
publication under upstream @agentmemory/* package names. Contributions should
follow CONTRIBUTING.md, and the downstream release history
is in CHANGELOG.md.
AI development disclosure
Most downstream modifications were generated and revised by OpenAI Codex from user-provided requirements and iterative acceptance requests. The repository owner did not manually review the source code. Validation is based on automated tests and live functional testing in the owner's Windows/Codex environment. No independent third-party code or security audit has been performed.
In short: AI-generated, user-tested, not manually code-reviewed.
Upstream attribution and license
This downstream is based on AgentMemory by Rohit Ghumare and contributors. See
NOTICE and upstream-source.json for the
attribution and exact source identity. The code is provided under the
Apache License 2.0.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.63MIT
- AlicenseAqualityAmaintenanceLocal-first persistent memory for Claude Code and OpenAI Codex CLI. A single Rust binary captures, distills, searches, and injects project memory across sessions via hooks, MCP, CLI, and localhost REST.31527MIT
- AlicenseNot gradedqualityCmaintenanceProvides local, project-aware memory for coding agents via MCP tools, lifecycle hooks, and a REST service, with no outbound network access.8,746Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.1,4872MIT
Related MCP Connectors
Persistent memory and cross-session learning for AI coding assistants (hosted remote MCP).
Persistent memory for AI agents. Search, store, and recall across sessions.
Persistent memory layer that saves and recalls your project context and preferences.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/M-T-D-N/agentmemory-codex-windows'
If you have feedback or need assistance with the MCP directory API, please join our Discord server