agentmemory-codex-windows
Related Servers
Alternatives to agentmemory-codex-windows
No user-submitted related servers found.
Related Servers
- 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.1533MIT
- AlicenseNot gradedqualityBmaintenanceEnables local-first personal knowledge management for Codex by turning conversations into a searchable archive, extracting durable facts, building a knowledge graph, and injecting relevant context into later sessions.9 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to retain cross-session memory of facts, decisions, and lessons with semantic search, while tracking user corrections as behavioral patterns and evolving self-improving frameworks over time. All processing runs locally through an MCP server and hooks, requiring no cloud service or API key.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to automatically recall and persist local project memory—such as decisions, constraints, goals, open loops, and milestones—across sessions via a secure, local MCP adapter.1Apache 2.0
- AlicenseBqualityBmaintenanceEnables Codex, Claude Code, and other MCP-capable clients on the same computer to share local SQLite long-term memory with Chinese keyword search, project scoping, revision history, and Markdown export. It does not automatically capture conversations or synchronize across devices.151MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.MIT
TDQS
Scored across 58 tools
The descriptions are unusually explicit about boundaries, repeatedly cross-referencing sibling tools (e.g. 'Use memory_recall for general topic searches', 'Use memory_graph_query for the separate entity/concept graph'). Still, with 58 tools there are several genuinely confusable clusters: memory_recall/memory_smart_search/memory_timeline/memory_file_history for retrieval, memory_patterns/memory_profile/memory_reflect/memory_insight_list for synthesis, and memory_export/memory_obsidian_export/memory_snapshot_create for output. The prose mitigates most of this, but an agent must read carefully to avoid misselection.
Every tool uses the memory_ prefix followed by a consistent snake_case verb_noun or resource_verb pattern (memory_save, memory_slot_create, memory_graph_upsert, memory_team_share). Sub-domains are grouped coherently (graph_*, slot_*, action_*, signal_*, sentinel_*, lesson_*), giving a predictable and highly legible naming scheme throughout.
58 tools is far beyond a practical single-server surface and effectively merges many subsystems (memory CRUD, entity graph, work items/actions, signals, team sharing, context slots, facets, diagnostics). While each tool is individually non-trivial, the sheer count creates cognitive overhead and makes the set feel like several servers bundled together. It is well past the 25+ threshold for 'too many'.
Coverage is remarkably thorough: full lifecycle for slots (list/get/create/append/replace/delete), actions, lessons, graph, facets, plus diagnostics, audit, archive, governance delete, export and sync. Minor gaps exist (lessons have no update, memories lack a direct edit/delete path beyond governance_delete), but core workflows have no dead ends.