Skip to content
Recall.
Get started

PERSISTENT MEMORY FOR CODING AGENTS

Great work shouldn’t
start from scratch.

Give Claude Code a memory that outlives the session.
Your decisions, your patterns, your next move. Still there.

Give your AI a memory Watch Recall in action

Start free · 500 memories · No credit card required

Try it: choose a memory to see it recalled.

Recall connects your project memoriesRECALL

The session ends. The context stays.

my-app / new sessionINTERACTIVE EXAMPLE

YOU ASK

How should we paginate the activity feed?

→ search_memories
Context recovereddecision

Use cursor-based pagination for the activity feed.

Offset pagination can skip or repeat items when new activity arrives.

#architecture
MEET YOUR EXISTING WORKFLOW
Claude Code
Claude Desktop
MCP clients
REST API

SEE RECALL IN ACTION

A little memory.
A different way to work.

Watch the walkthrough to see why Recall exists and how it fits into Claude Code.

Claude Code Forgets Everything. Here's My Fix.Watch on YouTube

LESS REPEATING. MORE BUILDING.

Your best thinking.
Ready for what’s next.

You solved it once. Recall gives your next session the context to build on it, from decisions and patterns to the errors you already worked through.

Decision saved Error captured Next step recorded

01 / REMEMBER

Keep the context worth keeping.

Save decisions through memory tools. Plugin hooks capture failing commands and session summaries.

my-appworkspace
another-projectworkspace

02 / ORGANIZE

One project. Its own memory.

Workspace isolation keeps each project’s context together. Confirm the workspace before storing new memories.

Your next session

03 / CONTINUE

Start somewhere better.

Search by meaning and recover relevant context when a session starts, even on another machine.

CONTEXT WITHOUT THE DISTANCE

Many minds.
One shared brain.

Different places. Shared project context.

The decision made in one time zone. The fix discovered in another. Give distributed teams a place to contribute what they learn, so the next person can build on it.

One account / shared project workspaceScroll-through example

Scroll to see the shared brain grow.

Or click a collaborator to add their contribution.

RECALL

Shared brain

Following your scroll

The project remembers.

1 / 3 added
  • Decisionfrom Europe

    The reason behind a choice.

    Use cursor pagination so new activity doesn’t move the page.

  • Fixfrom Asia-Pacific

    Next: Asia-Pacific’s fix.

    Scroll or choose this collaborator to add their knowledge.

  • Patternfrom Americas

    Next: Americas’s pattern.

    Scroll or choose this collaborator to add their knowledge.

For the next teammate, wherever they are.

Search this workspace to retrieve what others saved and put it to work in a new session.

Connect collaborators to the same Recall account and project workspace. What one person records can become context for the next.

Regions and memories above are illustrative. This example saves no data.
Find your team’s plan

DATA SANDBOXING, MADE UNDERSTANDABLE

A shared brain.
Clear boundaries.

Think of an account as the boundary, a workspace as a project’s room, and field encryption as protection for the record inside. Each layer has a different job.

FOLLOW THE THREE LAYERSINTERACTIVE EXAMPLE
Scroll to explore. Or jump to a step.01 / 03
01

Account

Your account is the first boundary.

Credentials identify your Recall account. PostgreSQL memory storage uses that account and the selected workspace to scope each query.

Your API keyIdentifies your account
Your Recall accountACCOUNT A
API project
Mobile project

Account identity is part of the memory request.

Another accountIts own memory scope

Outside this request

02

Project

A place for each project.

Workspaces separate project context by default. Linked workspaces and account-wide memories let you choose where context is shared.

Your Recall accountCHOOSE A PROJECT BELOW
Scroll to switch projects and bring in shared context. Or try the controls.

CONTEXT FOR API

  • Cursor pagination decisionproject
  • Background job conventionsproject
The other project’s records stay outside this example result.

Some context belongs across projects.Add an example account-wide checklist to either workspace.

03

Encryption

Protection for the content inside.

Recall supports AES-256-GCM field encryption for current memory-record content, using a key derived for each account. Coverage depends on configuration and record type.

A memory recordILLUSTRATION
typedecision
content

Use cursor pagination for the activity feed.

The readable text your agent works with.
tagsarchitecture, api

AES-256-GCM

A key derived
for each account.

With field encryption configured, the service can protect record content and decrypt it when reading it back.

Scroll to reveal the encrypted example. Or try it yourself.

This is an example of field encryption, not a check of your account’s settings.

Data sandboxing here means logical account and workspace separation within shared infrastructure.

Understand the protection and its current limits

What field encryption covers

Current record content
AES-256-GCM field encryption is supported when configured.
Search metadata & vectors
Metadata and PostgreSQL search vectors are not covered by this field encryption.
Version history
Historical record content is not currently covered by this field encryption.

How the boundaries work

  • These diagrams illustrate the PostgreSQL storage model: shared-table queries filter by account and workspace.
  • Project separation is logical. It does not allocate a dedicated server or execution environment to each workspace.
  • Encryption uses server-side, per-account key derivation. It is configuration-dependent; the current storage path can fall back to plaintext if encryption fails.
  • Restored workspace context must be confirmed again before new memories can be saved.

BUILT FOR REAL WORK

Keep going.
In more ways
than one.

Explore the use cases
01

Multi-Session Continuity

Come back to a feature with the decisions and next steps from the last session ready to retrieve.

02

Cross-Session Bug Hunts

Keep the hypotheses, failed attempts, and fixes you deliberately record, so the investigation can continue.

03

Decision Records

Save the choice and its reasoning together. Give the next session more than the final line of code.

04

Multi-Project Switching

Keep each codebase’s conventions in its own workspace, and confirm the project before saving new memories.

THE REST OF YOUR STACK, CONNECTED

Your tools have news.
Let your agent hear it.

Bring GitHub, Sentry, Linear, and other webhook events into your coding session. Route them to the right workspace, with your own instructions attached.

Explore Recall’s documentation
GitHubSentryLinear
Workspace event queuePRO + TEAM

The event. The project.
The context to act.

routed to my-app Claude Code

ROOM TO REMEMBER

Start free.
Keep more as you grow.

Persistent memory for your first project, your next project, and your whole team.

Free

Find your flow.

$0/ month

Start for free
  • 500 memories
  • 1 workspace
  • Semantic search
  • Claude Code plugin

Pro

7-day free trial

For the projects you live in.

$5/ month

Try Pro
  • 5,000 memories
  • 3 workspaces
  • Cross-session workflows
  • 1,000 webhook events / month

Team

Keep your team in context.

$15/ month

Get started with Team
  • 25,000 memories
  • 25 workspaces
  • 10 team members
  • 5,000 webhook events / month
Compare every plan feature
Recall plan features and allowances
FeatureFree$0 / monthPro$5 / monthTeam$15 / monthSelf-Hosted$12 / month
Memory
Memories5005,00025,000Unlimited
Workspaces13 (+ add-ons)†25 (+ add-ons)†Unlimited
Semantic searchIncludedIncludedIncludedIncluded
Cross-session workflowsNot includedIncludedIncludedIncluded
Auto-consolidationNot includedIncludedIncludedIncluded
Survives compactionIncludedIncludedIncludedIncluded
Webhooks
Webhook events / month—1,000 (+ packs)†5,000 (+ packs)†Unlimited
Webhook filters—25100Unlimited
HMAC signature verificationIncludedIncludedIncludedIncluded
Event history & replayNot includedIncludedIncludedIncluded
Workspace routingNot includedIncludedIncludedIncluded
Team & Security
Team members1110Unlimited
Shared memoriesNot includedNot includedIncludedIncluded
Audit loggingNot includedNot includedIncludedIncluded
REST APIIncludedIncludedIncludedIncluded
SupportCommunityPriorityPriorityCommunity

† Pro & Team add-ons: $0.99 per workspace / month. $1.99 per 1,000 webhook events / month.

Your infrastructure. Your memory.

Self-Hosted · $12 / month · Unlimited memories and workspaces.

Explore self-hosting

EVERY SESSION BUILDS ON THE LAST

Keep your momentum.

Make your next session the continuation it should be.

Start remembering for free

Create your account, get your API key, and install the plugin.

Run in Claude Code
/plugin marketplace add joseairosa/recall-claude-plugin
/plugin install recall@recall-claude-plugin

Then connect your Recall API key. View the full setup guide.