Persistent memory for Codex workflows

Squish gives coding workflows a durable memory layer, so project context survives beyond a single Codex session and stays inspectable by the developer.

Retain the decisions that matter

Capture the constraints, fixes, and architectural choices that usually disappear when a coding session ends.

Search before repeating work

Recall prior project context instead of asking an agent to rediscover the same implementation details from scratch.

How it works with Codex

Squish connects to Codex through the MCP protocol as a memory server. Your agent stores decisions and constraints during a session, then retrieves them automatically in future sessions so you don't lose project context.

Frequently Asked Questions

How does Squish integrate with Codex?

Squish runs as an MCP server. Codex connects to it via the standard MCP protocol to store and retrieve context.

Can I use Squish across multiple Codex projects?

Yes. Each project gets its own memory namespace. Cloud sync shares memory across machines.

What context does Squish preserve from Codex sessions?

Implementation decisions, bug fixes, architectural constraints, and project conventions.

Install Squish

Squish documentation