agentmemory-codex-windows

agentmemory-codex-windows

Enables persistent, project-scoped memory for OpenAI Codex Desktop and CLI on Windows, capturing prompts and responses through managed hooks, with federated recall across projects and optional local graph extraction.

Category
Visit Server

README

AgentMemory for Codex on Windows

Independent, Windows-native AgentMemory downstream for OpenAI Codex Desktop and Codex CLI.

English | 한국어 | 日本語

<p align="center"> <a href="https://github.com/M-T-D-N/agentmemory-codex-windows/actions/workflows/ci.yml"><img src="https://github.com/M-T-D-N/agentmemory-codex-windows/actions/workflows/ci.yml/badge.svg" alt="Windows CI" /></a> <img src="https://img.shields.io/badge/release-0.1.0--preview.1-orange" alt="0.1.0-preview.1" /> <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-blue" alt="Apache-2.0" /></a> </p>

[!IMPORTANT] This is an independent source-only Technical Preview. It is based on AgentMemory 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, and SessionEnd.
  • 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.

Version identities

Identity Value Meaning
Downstream release 0.1.0-preview.1 Public version and source tag
AgentMemory compatibility 0.9.29 CLI, MCP, package, API, export, and installed-runtime compatibility
Qualification revision r32 Internal build provenance, not a public version line
iii engine 0.11.2 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.0 through the repository's pinned package-manager declaration
  • The official iii engine 0.11.2 Windows executable whose SHA-256 matches packaging/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.exe

The 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.

[!WARNING] 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. Canonical data, 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
src/ AgentMemory compatibility source
packaging/windows-codex/ Supported Windows/Codex adapter, builder, installer, and tests
plugin/ Upstream-compatible plugin assets bundled into the source build; not the supported installation path
test/ Unit and security regression tests
benchmark/, eval/ Upstream-derived harnesses and historical reference results; not Windows preview qualification
integrations/ Compatibility integrations; not separately supported downstream products
upstream-source.json 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.mjs

The 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.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured