Memory

Agents that remember.

Every agent keeps a persistent memory of your preferences, your setup, and who it's dealt with — so it makes smarter calls and never repeats itself.

run #129
Lead Scout
J. Rivera contacted · Jun 3
New memory
memory.md
## What to remember
- Preferred tone: warm, concise
Saved across runs
run #130
Reconciler
recalls the saved contact
Duplicate skipped
Support Agent
recalls your tone rule
Reply in your style
The problem

Every run starts from zero.

Without memory, your agents forget your rules, who they've talked to, and what worked last time — so every run repeats the same setup instead of building on it.

Lead Scout

Re-researches the same prospects

Files a lead today, forgets it by tomorrow — and reaches out all over again.

Support Triage

Forgets your tone every time

Every reply is drafted from scratch, so nothing sounds like your team twice.

Reconciler

Re-asks what to match, nightly

The same setup questions, every run — none of last night’s decisions carried over.

Every agent

Starts every run from zero

Without memory, work is never cumulative — your agents relearn the basics instead of getting better.

How memory works

It remembers, so you never repeat yourself.

Persistent preferences

Your rules and context, remembered across every run.

Relationship memory

It knows who's been contacted, and when.

Full history

A complete, replayable record of everything it did.

The memory file

One durable file, written as it works

What the agent learns is saved to a plain Markdown memory file — and it stays with the agent from one run to the next, instead of resetting each time.

Run observations
run #127
Prefers concise replies
run #128
Contacted Acme on Jun 3 — don't re-contact
run #129
Weekly report format: CSV
Memory instructions

Define what Customer Support should remember between sessions.

Reset
## What to remember
- Durable preferences, decisions, working agreements…
In practice

Memory, at work.

01

Never re-contacts a lead

The agent won't re-contact a lead it already reached last month.

contacts.log
Acme Corp — J. Rivera
contactedJun 3
skip
Northwind — P. Adeyemi
never contacted
reach out
skip · already contacted
02

Your rules, applied automatically

It applies your tone and formatting rules without being re-told each time.

reply.draft
Draft to J. Rivera
Thanks for your note — your refund is being processed.
Expected by10 Jun 2026
Warm, concise toneDates as DD Mon YYYYSign off “The Ops team”
memory.md applied
03

Replay any past run

You scrub back through a video replay of any past run to see exactly what happened.

run-replay
replay starts when visible
00:12 Opened inbox
00:31 Matched 2 invoices
00:42 Flagged 1 mismatch
00:55 Requested review
00:00 / 01:20
Scoped by design

Every agent sees only what it should.

Memory is split into scoped buckets, and each agent gets its own read or write access per bucket — so sensitive context never leaks where it doesn't belong.

Memory buckets

Memory is bucketed by scope so an agent only sees what it needs. Read lets the agent recall facts; Read & write lets it save new ones.

viewing as Customer Support
Global memory
Cross-agent scratch memory shared by every agent in the workspace.
__global__
ReadRead/WriteNo access
Business Information
Company overview, strategy, key dates, founding info, team structure
company:business-info
ReadRead/WriteNo access
Products and Services
Product catalog, pricing, features, SKUs, service offerings
company:products
ReadRead/WriteNo access
Policies
Company policies, business rules, compliance, HR, governance
company:policies
ReadRead/WriteNo access
Operations
Processes, SOPs, vendor info, infrastructure, logistics
company:operations
ReadRead/WriteNo access
CRM
Customers, leads, contacts, deals, interactions, accounts
company:crm
ReadRead/WriteNo access
Shared memory

One shared memory, handed off between agents.

Agents write what they learn to a shared __global__ memory and read it back — so work started by one agent can be picked up by another.

On the shared memory4 agents
Lead Scout
writes → __global__
synced
Support Triage
← retrieves __global__
synced
Reconciler
← reads __global__
synced
Ops Agent
← receives __global__
synced

One pulse at a time — write, save, hand off.

__global__ · shared storelive
Lead Scout
writes → __global__
__global__
Cross-agent scratch memory shared by every agent
note saved
Support Triage
← retrieves __global__
Reconciler
← reads __global__
Ops Agent
← receives __global__
Knowledge corpus

Bring your own documents. Kept private.

Upload the reference material an agent should know. It's embedded and retrieved only when relevant — nothing leaves your workspace.

Knowledge corpusprivate to your workspace
Your document
policies.pdf
Private store6 chunks
Refund policy
Eligibility
How to file
Exceptions
Escalation
Contact
The agent asks
Draft a refund reply
Support agent
awaiting context

Chunks are embedded and retrieved; nothing leaves your workspace.

Across runs
Persistent.

Remembered across every run.

Per agent
Permissioned.

Scoped per agent.

Open format
Plain Markdown.

Open, read, and edit.

Memory makes an agent yours — start by defining one.

See Agents

Give your agents a memory.

Ready to put Actionist to work?

Start with a free instant demo, explore Actionist for yourself, or speak with our team about a deployment designed for your business.

Explore the documentation

Learn how agents, memory, schedules, triggers, channels, and cloud execution work together.

Still have questions?

Get answers about setup, security, pricing, deployment, and working with Actionist across your organization.