memory

Workspace memory

Understand shared workspace context, what belongs in it, and how workspace isolation keeps it separate from other workspaces.

Last verified 13 October 2026 · OpenbirdAI documentation

Workspace memory is durable context shared by the members of a workspace. It is how a team stops repeating the same background facts — business model, active clients, brand rules, standing targets — on every conversation.

This guide describes a capability that depends on the connected provider, the permissions granted to it, and your current plan. If the provider cannot supply the required data, OpenbirdAI reports it as unavailable rather than estimating.

What workspace memory is for

Stable business context that every answer should assume.
Definitions the team argues about, written down once.
Standing targets, constraints and preferences that apply to the whole workspace.
Notes attached to projects, clients or lines of business.

Workspace memory is not a document store. Put evidence-bearing material in a connected service and keep memory for context that shapes how answers should be produced.

Adding and updating memory

Open Ask in the correct workspace — check the workspace switcher first.
State the fact explicitly, for example "remember for this workspace that we price in USD but display LKR equivalents".
Confirm OpenFeather restates the fact in the way you intended.
Re-test it in a new conversation to confirm it persisted.

Keeping it accurate

Prefer updating an existing fact over adding a contradictory second one.
Delete or supersede facts that are no longer true; stale shared context is worse than none.
Keep personal preferences out of workspace memory.
Review workspace memory when a team member reports consistently odd answers.

When current operational configuration contradicts stored memory, the live configuration wins and the memory entry should be corrected.

Workspace isolation

Workspace memory is isolated. A fact stored in one workspace is never injected into another workspace's context, even for the same user. This is what prevents a personal workspace from leaking business context into a client workspace, or the reverse.

Confirm the active workspace before storing anything shared.
Use separate workspaces for separate clients or legal entities.
If a workspace was switched mid-conversation, start a new conversation to avoid blended context.

Memory hygiene across a team

Workspace memory is only as good as its upkeep. Assign someone to review it when goals change, remove facts that stopped being true, and prefer editing an existing entry over adding a second, slightly different one.

Stale shared context is worse than none, because every member trusts it.
If two members disagree about a stored fact, resolve it once and update the entry.
Review memory before onboarding someone, so their first answers are already well grounded.

Common questions

Why did a workspace fact I stored not appear?

Usually the request ran in a different workspace, or it was conversation context rather than durable memory. Check the switcher and restate the fact in the correct workspace.

Does everyone in the workspace share the same memory?

Yes, within that workspace only. Other workspaces and other workspaces' members see nothing of it.