Memory

An agent keeps memory so you do not repeat yourself. It is written text, not a hidden model state. You can read all of it and change all of it.

What goes into memory

Facts about your company that are true beyond one conversation. Which supplier belongs to which project. That fuel invoices are booked to Fleet. That one customer sends invoices as photos. That the month is closed on the fourth working day.

What does not go into memory: anything from a single run that has no meaning tomorrow, and anything a person has not confirmed.

How it is written

Each memory is one short entry with a heading, the fact itself, and the keys under which it should be found again. Before an agent starts a task it compares what you wrote with those keys and reads what matches, so the right handful of entries is in front of it instead of everything at once.

Learning happens through a gate

An agent does not quietly decide that something is now a rule. When it notices a pattern, it proposes it, and the entry becomes permanent when a person confirms it. That is the difference between an assistant that drifts and one you can hand a process to.

In the chat this looks like one sentence: “Written down. From now on every invoice from a fuel supplier is booked to Fleet.” Before that sentence, nothing changed.

What it cannot repeat

An agent reads what it was given access to and nothing else. Mailboxes, folders and records outside its connections are not part of its memory, and what it never read it cannot repeat.

Where you see it

In the agent settings: the rules card, the memory entries, and the generated index of what the agent knows. Changing a line there changes what the agent does on the next run.