Skip to main content

Work

What Managers Get Wrong About Agent Memory

Plain explanation of what an AI agent remembers between tasks and what it does not, and why that gap causes repeated instructions and confidently stale answers.

Written by Sicherhaven

You told the agent last week that the Nair account uses a different invoice format. This week it used the standard one again. It feels like being ignored.

It is not memory in the human sense. An AI agent remembers what it is given at the moment it works, and nothing else. Agent memory is really two different things: the records it can look up, and the notes someone chose to save from earlier conversations. If your instruction was not written into one of those, it was never remembered at all.

The two things people mix up

The first is the record. Customer details, project status, leave dates, policy documents, past invoices. These sit in a system, and the agent reads them when it works on something, which is why an agent should read the project board before answering a client. This is the part that behaves like memory in the way people expect.

The second is conversation history. What you said to the agent last Tuesday. Some of this may be saved, some of it is not, and the difference is a design decision somebody made rather than something the agent controls.

When a manager says "it forgot", they almost always mean the second. They gave a genuine instruction in the flow of a conversation, and that instruction was never written anywhere durable. It shaped that one piece of work and then it was gone.

Why you keep repeating yourself

Repetition is the most common complaint, and it has a mechanical cause.

An instruction given in conversation is treated as context for that task. An instruction written into a record is treated as a fact for every future task. They look identical when you type them. They behave completely differently.

So "remember that Priya approves anything over ten thousand" said in a chat window is a note that lasts as long as the chat. The same rule written into the record of how approvals work applies every time.

The practical habit that fixes most of this: whenever you find yourself telling an agent the same thing twice, stop and ask where that fact should live. It is nearly always a record, a procedure or a setting, not a message.

Why answers go stale

The other complaint is the opposite shape. The agent remembers something too well, and the thing it remembers is out of date.

This happens when a fact got saved once and nothing marks it as expired. A pricing note from last year. A team structure from before the reorganisation. A client contact who left. The agent has no way of knowing the world moved, because from its side the record still says what it says.

Human memory has a rough sense of age. You know that what you learned about a client two years ago might be stale. A saved record has no such instinct unless someone built one, usually as a date on the record or a rule that says facts of this kind expire.

If your agent keeps producing confidently wrong details, look for old records before you look at the agent. The same goes for absences, since an agent should see the leave calendar before it books a meeting.

What good looks like

An agent is most useful when the records it reads are the same records people work from, rather than a separate copy made for the AI. That is what changes when project boards, leave calendars and agents sit on one set of records.

That is the idea behind SicherOne: project management, HR and agents on one set of records, so an agent working on a task can see who owns it and who is on leave without anyone re-explaining. A human still approves agent output before it ships, which is also where stale facts get caught, because the approver knows the client changed contact in March even if the record does not.

Whatever tool you use, the same principle holds. The quality of what an agent remembers is the quality of what your organisation writes down.

Four habits worth adopting

  • Say instructions once, then write them somewhere durable. If you would not expect a new colleague to remember it from a passing remark, do not expect the agent to.
  • Date the facts that change. Prices, contacts, structures, entitlements.
  • When output is wrong, check the record before blaming the agent. Most wrong answers are correct answers to old data.
  • Keep the review step for anything with a fact in it that a person could verify from their own knowledge.

The mental model that works best is not a colleague with a memory. It is a very fast, very literal new starter who reads everything you hand them and forgets any conversation you did not write down. That model predicts almost every surprise you will have.

← All posts

We're building the future of community events and financial wellness

See how Eventify and WealthWise change the way people find events and manage money.

Get Started