“Why did we decide that?”
The reason lived in a chat that closed. Now someone has to guess, or decide it all over again.
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
new request
empty chat · no history
checkout/. Keeping the button green: team decision, red tested worse.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
best for
not for
updated
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.
The same change, asked in Claude Cowork on Monday and picked up in Codex on Thursday.
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.
ask checkout restyle
web/components/checkout/Keep the checkout button green?
empty chat · nothing pasted in
checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.Before it acts, it asks shared memory: what do we already know, and where does this live? One question, ranked answers.
ask checkout restyle
web/components/checkout/Keep the checkout button green?
empty chat · nothing pasted in
checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.Once it finds the right files, it saves a route: a short note that says where this kind of work lives.
ask checkout restyle
web/components/checkout/Keep the checkout button green?
empty chat · nothing pasted in
checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.You decide: keep the button green. That decision is saved as a memory, with the reason, linked to the task.
ask checkout restyle
web/components/checkout/Keep the checkout button green?
empty chat · nothing pasted in
checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.Days later a teammate opens Codex. A fresh chat with no history. The chat is empty. Shared memory is not.
ask checkout restyle
web/components/checkout/Keep the checkout button green?
empty chat · nothing pasted in
checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.It recalls the route and the decision, opens the right files, and keeps the button green. Nobody explained it twice.
ask checkout restyle
web/components/checkout/Keep the checkout button green?
empty chat · nothing pasted in
checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.ask checkout restyle
web/components/checkout/Keep the checkout button green?
empty chat · nothing pasted in
checkout/CheckoutButton.vue. The button stays green: team decision, red tested worse.Every run asks before it acts and saves on the way out. So the next run starts ahead.
Decisions, lessons and corrections, each with its reason. Ranked by meaning, the situations they apply in, recency and use.
why we did it
A map of where the files, documents, runbooks and data live, so no session has to search for them again.
where it lives
Every memory points back to the task that produced it. The reason and the work never drift apart.
traceable
Duplicates are grouped for a merge. Forgetting is soft and can be undone. Unanswered questions are listed. You choose what gets saved.
no noise
One question returns the decision, the place to look and the related work, ranked.
askCan we change the checkout button colour?
Keep the checkout button green. Red tested worse on conversion.
Checkout UI lives in web/components/checkout/
Checkout redesign
example data · ranked by meaning, situation, recency and use
Search spans every workspace you belong to. Each memory stays owned by its own team.
What did we decide about refunds?
A step that says "recall first" returns memories, routes and related tasks in a single query, before the agent touches anything.
{
"context_query": "payment webhook 500",
"returns": {
"memories": ["X-Sig header moved in v2"],
"routes": ["api/payments/webhook.py"],
"tasks": ["related: webhook retries"]
}
}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.
{
"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
}
}Tasks are searched by meaning, with a fallback when the index is down, plus structured filters and timezone-correct due and overdue views.
Recall fans out across every workspace you belong to. Each memory stays owned by its workspace, and every write lands in exactly one.
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.
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.
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.
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.
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.
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.
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.
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.
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.