Squish - Memory Infrastructure for AI Agents

SDK, MCP server, and CLI for persistent agent memory. Local-first. Zero dependencies.

Squish is memory infrastructure for AI agents. Use the TypeScript SDK to build memory-powered apps, the MCP server to plug into any compatible agent, or the CLI for quick operations. Local-first with optional Cloud sync.

Get Started in 30 Seconds

npm install -g squish-memory && squish install --all

That is it. Squish installs the CLI, starts the MCP server, and configures hooks for every coding agent it finds on your machine. No API keys. No config files. No Docker.

Related MCP server: Tages

Build on Squish

The @squish/sdk is the recommended way to build memory-powered AI applications:

import { SquishClient } from '@squish/sdk';
const client = new SquishClient({ dataDir: './memory' });
await client.remember('key decision', { type: 'decision' });
const context = await client.getContext();

SDK Documentation | API Reference

Pick Your Agent

Squish works with any MCP-compatible agent. Choose yours for a tailored quick start:

Claude Code

npm install -g squish-memory && squish install --all

Squish detects Claude Code and adds plugin hooks automatically. Your next session starts with full memory context. To verify:

squish context    # See what your agent remembers
squish status --stats  # Check memory health

Codex CLI (OpenAI)

Add Squish to your Codex MCP config:

{
  "mcpServers": {
    "squish": {
      "command": "squish-mcp",
      "args": ["--http", "--port", "8767"]
    }
  }
}

Codex now has persistent memory across sessions. Ask it "what did we decide about the database?" and it will recall your past decisions.

Cursor / Windsurf / Cline

Add the same MCP server block to your editor's MCP settings. One memory server, shared across all your editors and CLI agents.

OpenCode

squish install --all

OpenCode gets both MCP tools and auto-capture hooks. Decisions, constraints, and preferences are captured as you work.

Any MCP Client

{
  "mcpServers": {
    "squish": {
      "command": "squish-mcp",
      "args": ["--http", "--port", "8767"],
      "env": {
        "SQUISH_DB_PATH": "./squish-data"
      }
    }
  }
}

What Just Happened

After install, Squish runs in the background. Here is what it does:

1. Captures -- As you work, Squish watches for decisions, constraints, preferences, and context. It filters noise and stores what matters.

2. Ingests -- Drop files into the inbox directory. Images, audio, video, and documents are automatically extracted, described, and stored as searchable memories.

3. Stores -- Memories go into a local SQLite database with AES-256-GCM encryption. Nothing leaves your machine.

4. Retrieves -- When your agent starts a new session, Squish injects only the relevant memories (50-200 tokens, not 2,000).

5. Decays -- Old, low-value memories fade automatically. Your agent stays focused on what matters now.

squish remember "We chose PostgreSQL for the main datastore" --type decision
squish recall "database decisions"
squish sessions search "postgres migration"

Works with Every Agent

One memory server. Shared across all of them.

The SDK (@squish/sdk) works with any TypeScript or JavaScript environment -- not just coding agents. Build memory into web apps, CLI tools, backend services, or custom agent frameworks.

Why Squish

Most memory tools need a second LLM for embeddings and retrieval. That means extra API costs, latency, and infrastructure you have to manage.

Squish uses local embeddings by default. Zero LLM dependency. 1-5ms latency. $0 runtime cost in local mode.

Comparison

What Makes Squish Different

Squish is the only tool that combines all of these in a single package:

• SDK-first architecture -- @squish/sdk for building memory-powered apps in any TypeScript/JavaScript environment

• Local-first by default -- SQLite storage, TF-IDF embeddings, zero API keys needed

• MCP-native -- Works with every MCP-compatible agent out of the box

• Knowledge graph -- Reinforced relationships between memories, not just flat storage

• Decay system -- Old, low-value memories fade automatically so agents stay focused

• Hybrid search -- BM25 keyword + semantic similarity with RRF fusion

• Multimodal ingestion -- 27+ file types: images, audio, video, documents

• Zero external dependencies -- No Qdrant, no Postgres, no vector DB required in local mode

Core Concepts

Features

Memory Intelligence

• Auto-captures decisions, constraints, and preferences as you work

• Restores relevant context when an agent restarts

• Handles contradictions and temporal facts with expiration

• Graph-boosted retrieval connects related memories across sessions

• Contradiction detection flags conflicting information

• Temporal reasoning tracks when facts were true vs. now

• Confidence scoring adjusts memory relevance over time

• Decay system automatically ages low-value memories

Multimodal Memory

• Ingest images, audio, video, and documents into searchable memories

• Automatic text extraction via OCR, speech-to-text, and document parsing

• 27+ supported file types: JPEG, PNG, GIF, WebP, TIFF, HEIC, MP3, WAV, OGG, FLAC, M4A, MP4, WebM, AVI, MOV, MKV, PDF, DOCX, XLSX, PPTX, TXT, MD, CSV, JSON, XML, YAML, HTML, RTF

• File watcher for automatic inbox monitoring and ingestion

• LLM-generated descriptions for each ingested file

• Cross-connection finding via LLM consolidation across memory clusters

Session Search

• Search previous Claude Code, Codex, and OpenCode sessions

• Find related sessions by project path or file overlap

• Inspect past decisions, errors, and commands as evidence

• Separate from long-term memory -- raw session history, not distilled facts

Interfaces

• CLI: squish remember, recall, forget, link, context, stats (via status), clean, pin, sessions, doctor, cloud

• MCP Server: 15 tools for any MCP client -- remember, recall, forget, link, context, stats, inspect, skill, loadout, extract, feedback, places, sessions, tier, dedup (a 16th, squish_maintenance, appears when SQUISH_ENABLE_MAINTENANCE_TOOLS=true)

• Web UI: Local dashboard at localhost:37777 for visualizing memories

• Cloud Dashboard: Paid analytics and management at squishplugin.dev

Storage

• SQLite (local, default) or Squish Cloud team workspaces

• Hybrid retrieval: keyword + semantic similarity with RRF fusion

• AES-256-GCM encryption for sensitive memories

• Places routing: organize memories by project, feature, or context

• Full-text search with BM25 ranking

• Vector search with TF-IDF embeddings (768-dimensional)

Self-Hosting

Squish is local-first by design: the default mode IS self-hosted. Everything runs on your machine, no account required.

• Storage: single encrypted SQLite file (AES-256-GCM for sensitive memories) at SQUISH_DATA_DIR (default ~/.squish)

• Embeddings: local TF-IDF by default -- zero API keys, works fully offline. Optional providers (openai, ollama, google) if you want them

• LLM: optional and off by default (SQUISH_LLM_ENABLED=false) -- every core feature works without one

• Telemetry: none. Nothing leaves your machine in local mode

• License: MIT. Fork it, embed it, ship it

Point SQUISH_DATA_DIR at any volume or backup target and you are done. See Environment Flags for tuning knobs.

Environment Flags

Every flag ships with a safe default; nothing here is required for local use. See .env.example for the full annotated list.

Architecture

Three-Layer Memory Model

Connectors

Squish connects to your existing tools and ingests context automatically:

Connectors are available on Cloud tiers. Install with:

squish connect google-drive
squish connect github
squish connect slack
squish connect notion

Squish Cloud

Persistent memory across ChatGPT, Claude Desktop, Claude Code, and local agents. One account, synchronized everywhere.

Cloud features: OAuth 2.1 + PKCE login, cross-platform sync, team workspaces, admin dashboard, priority support.

Pricing

Sign up at squishplugin.dev -- 30 seconds, no credit card needed.

Benchmarks

Squish is tested against real-world memory retrieval tasks and synthetic benchmarks.

Full benchmark details: docs/BENCHMARK.md

Documentation

FAQ

What is Squish?

Squish is memory infrastructure for AI agents. It provides a TypeScript SDK, an MCP server, and a CLI for persistent agent memory. Use the SDK to build memory-powered apps, plug the MCP server into any compatible agent, or use the CLI for quick operations. Local-first with optional Cloud sync. Think of it as a brain that persists between sessions -- your agents remember decisions, constraints, preferences, and context without you having to re-explain everything.

Does Squish require an API key?

No. Squish works locally by default with zero API keys. It uses local embeddings (TF-IDF) and SQLite storage. You can optionally configure an external LLM for enhanced reasoning, but it is not required. An API key is only needed if you want to use the paid Squish Cloud for cross-device sync.

How does Squish compare to mem0 or agentmemory?

Squish is the only option that works locally with zero external dependencies AND provides a TypeScript SDK. mem0 requires Qdrant (a vector database) and cloud API calls. agentmemory requires iii-engine. Letta and Zep require Postgres. Squish uses SQLite and local embeddings by default. See the full comparison in the Why Squish section above.

Can I use Squish with multiple AI agents?

Yes. Squish works with any MCP-compatible agent. One memory server is shared across Claude Code, Cursor, Codex, Copilot, Gemini CLI, and any other agent that supports MCP. Memories are available to all connected agents. You can also use the SDK directly in any TypeScript/JavaScript environment.

Is my data private with Squish?

Yes. In local mode, all data stays on your machine in an encrypted SQLite database. Nothing is sent to any cloud service. AES-256-GCM encryption protects sensitive memories. Cloud sync is opt-in and additive: data moves over TLS, connector credentials are encrypted at rest with AES-256-GCM, and synced memories live in the cloud database under your account's access controls -- which is exactly why local remains the default and sync stays optional.

What is the difference between recall and sessions?

squish recall searches your long-term memory -- distilled facts, decisions, and preferences that Squish has captured and organized. squish sessions search searches raw past agent runs -- the actual messages, commands, and file changes from previous Claude Code, Codex, OpenCode, or Gemini CLI sessions. Recall gives you what the system decided to remember. Sessions give you the evidence.

Every recall result carries a recall assessment with a verdict: confident (top result is reliable), qualified (usable but treat with care), or no_reliable_memory (nothing trustworthy found -- say so rather than guessing). Feed verdicts back via squish_feedback: confirm, used, or contradict.

Contributing

See docs/CONTRIBUTING.md for guidelines on how to contribute to Squish.

License

MIT -- see LICENSE for details.

Star the Repo

If Squish helps your project, consider starring the repo. It helps other developers find memory tools for their AI agents.