M-T-D-N/agentmemory-codex-windows

Independent, Windows-native AgentMemory downstream for OpenAI Codex Desktop
and Codex CLI.
English | 한국어 | 日本語
Install without building · Operating guide · Validation and limits · Release notes
> [!IMPORTANT]
> This is an independent Technical Preview. It is based on
> AgentMemory v0.9.30, 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.
Start here
The published preview.17 release packages AgentMemory 0.9.30 with the downstream-patched iii engine/SDK 0.22.1. The same installer supports an empty target, an owned managed installation, or an explicitly identified original upstream 0.9.29/0.9.30 file-backed installation. You do not need to install upstream first.
Preview.17 is a qualified Windows technical preview. The release page contains all four verified assets, and the tagged source passed Windows CI. Keep the preview.16 launcher and assets together when using that historical release. See the preview.17 operating and validation notes.
1. Check Windows x64, Node.js 24+, Windows PowerShell 5.1 and Codex desktop, then follow the pinned installer guide. The published release includes a prebuilt runtime; source builds are optional.
2. Preview the selected installation path, then use --execute. For an empty target the default path prepares, activates and validates the service; --fresh and --activate-prepared remain available for separate phases. Connect Codex MCP after service validation.
3. If a step fails, use support and recovery guidance. Report the release and failing phase with a short redacted error; do not attach memory databases or credentials.
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 audited, target-scoped live graph provenance correction with dry-run
previews. Manual graph writes with multiple source groups must map every node
and edge through zero-based sourceIndexes, or explicitly opt into shared
provenance with sharedSources: true.
- Supports audited recovery of proven empty observations through the existing
REST forget endpoint, with exact IDs, version checks and preserved graph cursors.
- 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 58 MCP tools. Its MCP surface
is 58 tools, 6 resources, and 3 prompts; it also has 143 endpoints on port 3111,
12 portable hooks, and 17 skills. The supported Windows profile intentionally
activates only the four managed hooks listed above.
For audits, MCP memory_recall, memory_smart_search, and memory_timeline
accept trackAccess: false to avoid access-count reinforcement. The default
remains true; visibility, project boundaries, and recovery guards still apply.
Graph query shards are rebuildable indexes in the same iii StateModule as the
canonical graph. Missing or dirty indexes use a bounded snapshot with a warning;
only an explicit snapshot rebuild refreshes them.
Release changes are recorded in CHANGELOG.md. Source tags
identify public releases; each build manifest records its own qualification.
Changes in preview.17
- Verify source, actual test logs, immutable payload, Windows installation scenarios and confirmed operating evidence before producing a distribution.