Persistent memory for Cursor

Keep useful project knowledge available across Cursor sessions without turning a single prompt file into an ever-growing source of stale context.

Remember more than a prompt file

Store durable facts, preferences, decisions, and constraints as searchable memory rather than manually maintaining every detail in one static file.

Keep the developer in control

Review, edit, and remove stored memory. Squish is local-first, so the default runtime does not require sending project context to a hosted service.

How it works with Cursor

Squish runs as a separate MCP server that Cursor connects to. While Cursor's built-in memory is session-scoped, Squish provides cross-session persistence with semantic search and automatic belief derivation from your coding observations.

Frequently Asked Questions

How is Squish different from Cursor's built-in memory?

Cursor's memory is session-scoped. Squish provides persistent, cross-session memory with semantic search and belief derivation.

Can I use Squish alongside Cursor's rules file?

Yes. Squish complements .cursorrules by providing dynamic, evolving memory instead of static rules.

Does Squish slow down Cursor?

No. Squish runs as a separate MCP server. Memory operations are fast (6ms search, 39 ops/sec).

Install Squish

Squish documentation