Memory

Private and shared memory

Each agent has two scopes.

Agents without a business use the account owner's shared fallback. Switching businesses changes the shared organization context available to that business's agents.

Default memory

Each agent starts with a private SOUL.md file for its durable identity and working guidance. Shared business memory starts with ORG.md, which records people, agents, roles, and the organization structure.

Agents can create additional Markdown files for durable concepts such as customers, finance, product, brand, or a named initiative. A separate file is useful when the concept has enough detail to maintain over time.

What belongs in memory

Temporary task instructions, raw research dumps, and large source documents usually belong in the conversation or Files instead.

Never store secrets

Do not store passwords, API keys, access tokens, private keys, recovery codes, or other secrets in memory. Pazi checks memory writes for sensitive-looking material, but you should still use the secure credential flow.

Review and edit memory

Open All Docs → Memory for the selected agent. You can inspect private and shared entries, edit Markdown, delete stale files, search, and refresh the list.

When facts conflict, edit the existing entry so the active truth is clear. Avoid keeping two contradictory statements and hoping the agent chooses the right one.

Import Markdown

You can import Markdown files into private memory. Imports must be Markdown, non-empty, within the displayed size limit, and free of sensitive-looking material. Review the imported scope and content after it succeeds.

Use Files rather than memory for long documents, code, spreadsheets, or source archives. Memory should remain concise enough to guide every relevant run.

Shared-memory collaboration

Shared memory is versioned so business-level changes have a recoverable history. More than one agent can still edit shared memory at the same time, so coordinate major organization or strategy changes instead of asking several agents to rewrite the same file concurrently.

When creating or changing an agent's role, update ORG.md so people and agents understand who owns what.

Memory updates in chat

When an agent successfully updates a memory file, chat can show a Memory updated element. Treat that as an audit signal, then open Memory to inspect the complete file when the change matters.

You can also tell the agent explicitly what should or should not be remembered.