OpenAI's terminal agent with cross-session memory
Your specialist implementer that finally remembers the spec
The Problem
Codex CLI is OpenAI's answer to terminal-based AI coding. It reads your codebase, makes changes, runs tests. It's the specialist implementer you always wanted.
Except it has the memory of a mayfly.
Every session starts from scratch. The coding conventions you established? Gone. The architecture decisions from yesterday's four-hour session? Vanished. The reason you chose PostgreSQL over MongoDB? You'll explain it again. And again. And probably again tomorrow.
Codex can implement anything — as long as you explain everything. Every. Single. Time.
How Stompy Helps
Stompy gives Codex CLI a persistent memory that survives session restarts — via three integration paths that all connect to the same underlying store.
MCP: Use codex mcp add for native tool integration. Codex calls lock_context and recall_context alongside its other tools.
CLI: Shell commands — stompy lock, stompy recall, stompy search. Perfect for scripted workflows or when you want to pre-load context before a session.
REST API: HTTP endpoints at /api/v1/agent/memory/*. Ideal for CI/CD pipelines, custom orchestration, or feeding context from external systems.
Three paths, one brain. Lock context via the API in your CI pipeline, recall it via MCP in your Codex session. The memory store doesn't care how you got there.
Integration Walkthrough
Path 1: Connect via MCP (native integration)
Use Codex CLI's built-in MCP support to add Stompy as a tool provider.
# Add Stompy to Codex CLI via MCPcodex mcp add stompy \--transport sse \https://mcp.stompy.ai/sse \--header "Authorization: Bearer $STOMPY_TOKEN"
Codex uses memory tools automatically
Once connected, Codex calls Stompy tools as part of its planning and implementation workflow.
# Session 1: Codex learns your project patternscodex "refactor the payment module to use the strategy pattern"# → lock_context(topic="payment_patterns", content="Strategy pattern with...")# Session 12: Codex remembers the architecturecodex "add a new payment provider"# → recall_context(topic="payment_patterns") — implements consistently
Path 2: Use Stompy CLI for pre-loading context
Load context before starting a Codex session, or save findings from any terminal.
# Pre-load architecture decisions before a Codex sessionstompy lock --topic "architecture" \--content "Monorepo with packages/api, packages/web, packages/shared"# Codex session picks it up via MCPcodex "add a new shared utility for date formatting"# → Codex recalls architecture context automatically
Path 3: REST API for CI/CD integration
Store deployment context, test results, or build metadata that Codex can reference.
# CI pipeline stores test resultscurl -X POST https://api.stompy.ai/api/v1/agent/memory/store \-H "Authorization: Bearer $STOMPY_TOKEN" \-H "Content-Type: application/json" \-d '{"topic": "last_ci_run", "content": "3 tests failing in auth module..."}'# Codex session reads CI contextcodex "fix the failing auth tests from the last CI run"# → Recalls last_ci_run, knows exactly what's broken
Multi-agent orchestration: Claude architects, Codex implements
Use Claude Code for high-level design, Codex for implementation — same memory layer.
# Claude designs the featureclaude "design the notification system architecture"# → lock_context(topic="notification_arch", content="Event-driven with...")# Codex implements it — with full architectural contextcodex "implement the notification system"# → recall_context(topic="notification_arch")# → Builds exactly what Claude designed, no re-explaining
What You Get
- Three integration paths: MCP, CLI, and REST API — unified memory store
- Multi-agent orchestration: Claude architects, Codex implements, both share context
- CI/CD integration: store build context via API, recall it in coding sessions
- Session continuity: pick up where you left off across restarts and machine switches
- Project isolation ensures separate codebases stay completely independent
Ready to give Codex CLI a memory?
Join the waitlist and be the first to know when Stompy is ready. Your Codex CLI projects will never forget again.