shared memory for AI agents: Teach it once. Every AI remembers.

ConvOps shared memory is one memory store for every AI agent your team uses. Decisions, reasons and where things live are saved as your team works, so the next chat, in any AI tool, starts knowing them instead of starting from zero.

recall before acting · capture on the way out · nothing stored without you

example · Claude Coworkmonday

new request

Keep the checkout button green. Red tested worse.
memory saved · decision · linked to task
team memory
memoryButton stays green
routeweb/…/checkout/
example · Codex · new chatthursday

empty chat · no history

Restyle the checkout page.
recall · 1 decision · 1 route
Opening checkout/. Keeping the button green: team decision, red tested worse.
in short

How do AI agents share memory in ConvOps?

Through shared memory: decisions, reasons and where things live are saved as the team works, and one recall call brings them back at the step that needs them.

ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.

key facts · october 2026

  • One context_query call returns memories, routes (where code and documents live) and related tasks.
  • Recall happens where you write it into a step, for example "recall first" at the start of a bug fix.
  • Automatic capture is three settings, off by default. Nothing is stored unless you or a step asks for it.
  • One recall searches every workspace you belong to, while each memory stays owned by exactly one workspace.
  • The memory is the same for every AI client, so a decision saved from Claude Code is recalled in Cursor or ChatGPT.

best for

  • Teams tired of re-explaining the same decisions to every new chat.
  • Several people and several AI clients working on the same codebase or process.
  • Keeping what a person knew when they leave the team.

not for

  • Personal chat memory about you. ConvOps remembers how the work is done, not your preferences.
  • A general vector database for your application. ConvOps shared memory serves agents working through ConvOps.

updated

the problem

Every new chat starts from zero.

Your team already made the decision, found the files and learned the lesson. Then the chat closed.

“Why did we decide that?”

The reason lived in a chat that closed. Now someone has to guess, or decide it all over again.

“Where does that live again?”

Every new session searches the same folders, wikis and runbooks again, and asks the same questions.

“What happens when someone leaves?”

What they knew walks out with them. The AI never learned it in the first place.

watch it work

One decision, two tools, zero re-explaining.

The same change, asked in Claude Cowork on Monday and picked up in Codex on Thursday.

01you, in Cowork

A request becomes a task.

Someone asks for a change from Claude Cowork. ConvOps turns it into a task with a workflow, so the work has a home before anyone touches it.

example · Claude Coworkconnected to ConvOps
Can we restyle the checkout page?
task created · Checkout restyle · workflow attached
taskCheckout restyle
look first
build
approveapproval
ship
example · ConvOps · recallbefore acting

ask checkout restyle

memoryBrand colours come from tokens, never hex
routeCheckout UI: web/components/checkout/
taskCheckout redesign (done)
example · repositoryexploring
  • web/
  • components/
  • checkout/
  • CheckoutButton.vue
  • Summary.vue
  • account/
  • api/
route savedCheckout UI lives in web/components/checkout/
waiting for approval

Keep the checkout button green?

Change itKeep green
example · Codex · new chatno history

empty chat · nothing pasted in

team memory
decisionButton stays green
routecheckout/ lives here
lessonColours come from tokens
example · Codexright first time
Make the checkout page match the new brand.
recall · 2 memories · 1 route
Opening checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.
checkout
Pay now
02the AI

The AI looks first.

Before it acts, it asks shared memory: what do we already know, and where does this live? One question, ranked answers.

example · Claude Coworkconnected to ConvOps
Can we restyle the checkout page?
task created · Checkout restyle · workflow attached
taskCheckout restyle
look first
build
approveapproval
ship
example · ConvOps · recallbefore acting

ask checkout restyle

memoryBrand colours come from tokens, never hex
routeCheckout UI: web/components/checkout/
taskCheckout redesign (done)
example · repositoryexploring
  • web/
  • components/
  • checkout/
  • CheckoutButton.vue
  • Summary.vue
  • account/
  • api/
route savedCheckout UI lives in web/components/checkout/
waiting for approval

Keep the checkout button green?

Change itKeep green
example · Codex · new chatno history

empty chat · nothing pasted in

team memory
decisionButton stays green
routecheckout/ lives here
lessonColours come from tokens
example · Codexright first time
Make the checkout page match the new brand.
recall · 2 memories · 1 route
Opening checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.
checkout
Pay now
03the AI

It learns where things are.

Once it finds the right files, it saves a route: a short note that says where this kind of work lives.

example · Claude Coworkconnected to ConvOps
Can we restyle the checkout page?
task created · Checkout restyle · workflow attached
taskCheckout restyle
look first
build
approveapproval
ship
example · ConvOps · recallbefore acting

ask checkout restyle

memoryBrand colours come from tokens, never hex
routeCheckout UI: web/components/checkout/
taskCheckout redesign (done)
example · repositoryexploring
  • web/
  • components/
  • checkout/
  • CheckoutButton.vue
  • Summary.vue
  • account/
  • api/
route savedCheckout UI lives in web/components/checkout/
waiting for approval

Keep the checkout button green?

Change itKeep green
example · Codex · new chatno history

empty chat · nothing pasted in

team memory
decisionButton stays green
routecheckout/ lives here
lessonColours come from tokens
example · Codexright first time
Make the checkout page match the new brand.
recall · 2 memories · 1 route
Opening checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.
checkout
Pay now
04you decide

You decide. The reason is kept.

You decide: keep the button green. That decision is saved as a memory, with the reason, linked to the task.

example · Claude Coworkconnected to ConvOps
Can we restyle the checkout page?
task created · Checkout restyle · workflow attached
taskCheckout restyle
look first
build
approveapproval
ship
example · ConvOps · recallbefore acting

ask checkout restyle

memoryBrand colours come from tokens, never hex
routeCheckout UI: web/components/checkout/
taskCheckout redesign (done)
example · repositoryexploring
  • web/
  • components/
  • checkout/
  • CheckoutButton.vue
  • Summary.vue
  • account/
  • api/
route savedCheckout UI lives in web/components/checkout/
waiting for approval

Keep the checkout button green?

Change itKeep green
example · Codex · new chatno history

empty chat · nothing pasted in

team memory
decisionButton stays green
routecheckout/ lives here
lessonColours come from tokens
example · Codexright first time
Make the checkout page match the new brand.
recall · 2 memories · 1 route
Opening checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.
checkout
Pay now
05a teammate, in Codex

A new tool, an empty chat.

Days later a teammate opens Codex. A fresh chat with no history. The chat is empty. Shared memory is not.

example · Claude Coworkconnected to ConvOps
Can we restyle the checkout page?
task created · Checkout restyle · workflow attached
taskCheckout restyle
look first
build
approveapproval
ship
example · ConvOps · recallbefore acting

ask checkout restyle

memoryBrand colours come from tokens, never hex
routeCheckout UI: web/components/checkout/
taskCheckout redesign (done)
example · repositoryexploring
  • web/
  • components/
  • checkout/
  • CheckoutButton.vue
  • Summary.vue
  • account/
  • api/
route savedCheckout UI lives in web/components/checkout/
waiting for approval

Keep the checkout button green?

Change itKeep green
example · Codex · new chatno history

empty chat · nothing pasted in

team memory
decisionButton stays green
routecheckout/ lives here
lessonColours come from tokens
example · Codexright first time
Make the checkout page match the new brand.
recall · 2 memories · 1 route
Opening checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.
checkout
Pay now
06the AI

Right the first time.

It recalls the route and the decision, opens the right files, and keeps the button green. Nobody explained it twice.

example · Claude Coworkconnected to ConvOps
Can we restyle the checkout page?
task created · Checkout restyle · workflow attached
taskCheckout restyle
look first
build
approveapproval
ship
example · ConvOps · recallbefore acting

ask checkout restyle

memoryBrand colours come from tokens, never hex
routeCheckout UI: web/components/checkout/
taskCheckout redesign (done)
example · repositoryexploring
  • web/
  • components/
  • checkout/
  • CheckoutButton.vue
  • Summary.vue
  • account/
  • api/
route savedCheckout UI lives in web/components/checkout/
waiting for approval

Keep the checkout button green?

Change itKeep green
example · Codex · new chatno history

empty chat · nothing pasted in

team memory
decisionButton stays green
routecheckout/ lives here
lessonColours come from tokens
example · Codexright first time
Make the checkout page match the new brand.
recall · 2 memories · 1 route
Opening checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.
checkout
Pay now
example · Claude Coworkconnected to ConvOps
Can we restyle the checkout page?
task created · Checkout restyle · workflow attached
taskCheckout restyle
look first
build
approveapproval
ship
example · ConvOps · recallbefore acting

ask checkout restyle

memoryBrand colours come from tokens, never hex
routeCheckout UI: web/components/checkout/
taskCheckout redesign (done)
example · repositoryexploring
  • web/
  • components/
  • checkout/
  • CheckoutButton.vue
  • Summary.vue
  • account/
  • api/
route savedCheckout UI lives in web/components/checkout/
waiting for approval

Keep the checkout button green?

Change itKeep green
example · Codex · new chatno history

empty chat · nothing pasted in

team memory
decisionButton stays green
routecheckout/ lives here
lessonColours come from tokens
example · Codexright first time
Make the checkout page match the new brand.
recall · 2 memories · 1 route
Opening checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.
checkout
Pay now
the loop

Look first. Work. Keep what you learned.

Every run asks before it acts and saves on the way out. So the next run starts ahead.

recallask shared memory
workright files
decideapproval
capturememory + reason
next runstarts ahead
what it remembers

What, where, and why.

Memories: the what

Decisions, lessons and corrections, each with its reason. Ranked by meaning, the situations they apply in, recency and use.

why we did it

Routes: the where

A map of where the files, documents, runbooks and data live, so no session has to search for them again.

where it lives

Linked to the work

Every memory points back to the task that produced it. The reason and the work never drift apart.

traceable

Kept healthy

Duplicates are grouped for a merge. Forgetting is soft and can be undone. Unanswered questions are listed. You choose what gets saved.

no noise

try it

Ask shared memory.

One question returns the decision, the place to look and the related work, ranked.

try a question
example · ConvOps · recall3 results

askCan we change the checkout button colour?

#1memorydecision · linked to task "Checkout redesign"

Keep the checkout button green. Red tested worse on conversion.

meaning
situation
recency
use
#2routeroute · saved by the AI

Checkout UI lives in web/components/checkout/

meaning
situation
recency
use
#3tasktask · done

Checkout redesign

meaning
situation
recency
use

example data · ranked by meaning, situation, recency and use

across teams

One question. Every workspace.

Search spans every workspace you belong to. Each memory stays owned by its own team.

one question

What did we decide about refunds?

SupportRefunds over 200 need a lead to approve.
FinanceRefunds post to the same month as the sale.
ProductSelf-serve refunds within 14 days.
Supportworkspace
Financeworkspace
Productworkspace
the difference

Re-explaining vs remembered.

  • Paste the same context into every session
  • The fix is in a chat log somewhere
  • The agent re-greps the codebase every run
  • Knowledge leaves when the session ends
  • Each workspace is a silo you query separately
  • One query returns it, ranked and current
  • The decision is a memory linked to the task
  • Routes already say where things live
  • Capture is wired into the step that produced it
  • One recall searches every workspace you belong to

Recall is one call

A step that says "recall first" returns memories, routes and related tasks in a single query, before the agent touches anything.

payload
{
  "context_query": "payment webhook 500",
  "returns": {
    "memories": ["X-Sig header moved in v2"],
    "routes": ["api/payments/webhook.py"],
    "tasks": ["related: webhook retries"]
  }
}
Recall is a step you write, not magic.

Capture rides the step

Advancing a step can carry the decision and the why. A require_context gate makes it mandatory. Automatic capture is a set of workspace settings that ship off.

payload
{
  "workflow_advance": {
    "context": "root cause: X-Sig header
       moved in v2. Fixed in webhook.py"
  },
  "org_settings": {
    "brain.auto_memory_progress": true,
    "brain.auto_memory_decisions": false
  }
}
The why survives the session that discovered it.

Semantic task search

Tasks are searched by meaning, with a fallback when the index is down, plus structured filters and timezone-correct due and overdue views.

Search spans, ownership does not

Recall fans out across every workspace you belong to. Each memory stays owned by its workspace, and every write lands in exactly one.

In and out

A bulk store seeds shared memory from an existing knowledge base, so a new region or team starts with it. Memories that match a filter export as CSV or JSON for an audit or a records review.

questions

Agent memory questions, answered.

What is shared memory for AI agents in ConvOps?

It is ConvOps shared memory: memories that hold what your team decided and why, and routes that say where things live. One query returns both, plus related tasks, to any AI client connected over MCP. Example: a support agent recalls the refund rule, a legal reviewer recalls last month's ruling on a clause, an engineer recalls why a setting changed.

Is this RAG over my documents?

No. ConvOps memory is operational: what past runs learned, what was decided and why, and where things live. Recall is ranked by semantic relevance, the situations a memory applies in, recency and how often agents actually use it, not by document similarity alone. Your documents stay where they are, and a route can point at them.

What gets stored automatically?

Nothing you did not choose. In ConvOps, passing context on a step advance stores a memory on purpose, and a require_context gate makes recording the why mandatory for that step. Workspace settings for automatic capture exist, and they ship off. Shared memory holds what your workflows decided to keep.

What is the difference between memories and routes?

In ConvOps, memories are WHAT: decisions, knowledge, preferences and procedures. Routes are WHERE: a map of files, documents, runbooks and the pages of other tools. One context query returns both, plus related tasks, so the agent neither works the answer out again nor searches the same ground again.

Does memory get noisy over time?

It can, so ConvOps builds hygiene in. A duplicate scan groups near-identical memories for a merge, routes with no hit in 30 days are listed, and forgetting is soft, so a forgotten memory can be brought back. Questions shared memory could not answer are listed too, so someone can add the answer once.

Does recall cross workspaces?

Search does; ownership does not. In ConvOps one query fans out across every workspace you belong to, but each memory stays owned by its workspace and isolated at the database layer, and every write lands in exactly one. Example: a refunds question returns the support rule and the finance rule, each badged with its workspace.

Can I bring knowledge in, or take it out?

Yes, both. ConvOps takes a bulk store, so a team opening a new region can seed shared memory from an existing knowledge base and every recall-first step uses it from day one. Memories that match a filter export as CSV or JSON, which suits an audit or a records review.

Is task search keyword or semantic?

Semantic. ConvOps indexes every task and searches it by meaning, with an automatic fallback when the search index is unavailable. A full set of structured filters sits beside it: dates, hierarchy, status, and due and overdue views that take an explicit time zone.