Skip to content

Memory

Agents do not start from zero in every conversation. Shara keeps a memory: short notes about your company, your team and your way of working, which the agents look up when they are relevant. Memory is included in every plan, from First to Concerto Local.

This page explains what is stored, who can see it and how you control it. For the file that fixes tone and rules, see Agent identity; memory and identity work together.

A memory is a fragment: a title, a text of up to 20,000 characters, optional tags and an importance from 1 to 10. For example:

  • Title: Preferred delivery times. Text: Our customers expect delivery notes before 10:00.
  • Title: Key accounts. Text: Acme and Norte Foods are priority accounts; always copy the sales director.

Each fragment is indexed by meaning, not only by keywords. When an agent starts a task it searches for the fragments closest to the request and uses them as context. Saving a fragment spends a small amount of STU (it has to be indexed).

  • The agents. While they work, they can save a fact, a decision or a preference, and forget one that is out of date. Amadeus saves at company level; a departmental agent saves in its own memory.
  • You. You can add, edit and forget memories from the Memory page of the app.

An agent does not need your approval to save or forget a memory. That is why the page exists: so you can review what your team has learned.

Every memory belongs to one scope, which decides who can see it.

Scope In the app Who sees it
Company Company Everyone in your company.
Department Everyone in your company. It is tagged with a department so agents use it for that area.
Agent Agents People whose department matches the agent’s department.
User Personal Only you. Nobody else in your company can see it, not even a company administrator.

Memory never crosses between companies. Your memory is only searched when your own company’s agents work.

Personal memory is created in your name only: nobody can write a personal memory on behalf of someone else.

Action Who
Save, edit or forget personal memory Each person, on their own.
Save, edit or forget company and agent memory Every role except Viewer.
Promote a memory to the company identity Owner (CEO) and Administrator.

The Viewer role is read-only, so it cannot change shared memory. The full role list is in Roles and permissions.

Open Memory in the app. You can:

  • Search by meaning (“what do we know about late payers?”) and filter by scope (All, Company, Agents, Personal), by agent and by age (last week, month or year).
  • Add a memory yourself, and edit the title or the text of an existing one. An edited fragment is indexed again.
  • Forget a fragment with the Forget button. From that moment it stops appearing and agents stop using it. Forgetting is a logical deletion: the record is marked as deleted instead of being physically wiped, and the app has no button to bring it back. Memory is never deleted by age: only you delete it.

Two details worth knowing:

  • Search shows how well each result matches (“87 % match”).
  • If two people edit the same fragment at the same time, the second save is refused with a conflict, so nobody overwrites the other’s change by accident.

Some memories deserve to become permanent rules. An owner (CEO) or administrator can promote a fragment to the company identity (IDENTITY.md) with Promote to the company identity. You write a short reason, and the text is added as a new versioned patch. The reason and the change are recorded in the audit log.

Use memory for things that are true and useful to know (“Acme pays at 60 days”). Promote to identity what must be always applied (“never promise a delivery date in writing”).

  • Memory lives in the European Union, like the rest of your company’s data.
  • It is included in the company export; personal memory of other people is not. See No vendor lock-in.
  • Memory is separated by company at every layer. See Security and compliance.