osFoundry / Platform
Memory groups (Studio)
Wire surfaces into memory groups with retention, write mode and PII redaction policies.
What it is
Memory groups are how you decide what your AI agents remember, and under what rules. In osFoundry Studio you take the surfaces an agent works across — a chat thread, an app, a code repository, a knowledge base, a data table — and wire them into a named memory group. Everything in that group shares one memory context governed by three policies: retention (how long remembered items are kept before they age out), write mode (whether the group is read-only, append-only, or freely writable, so you control which surfaces can add to memory versus only read from it), and PII redaction (strip personal data out before anything is written to the store).
Because osFoundry is a bring-your-own-key desktop workspace, these memory groups live with the rest of your Studio configuration rather than on a vendor's servers. The retention, write-mode and redaction policies are applied where the memory is written and read, so a group scoped to keep data on your device keeps it there. That matters when a memory group spans a customer support chat and a data table full of names and emails: PII redaction lets the agent carry forward the useful context without persisting the identifiers, and retention keeps stale context from accumulating indefinitely.
Practically, memory groups let one team of agents stay coherent across the surfaces it touches without leaking context sideways into unrelated work. You define the boundary — which surfaces are in, which are out — and the policies travel with the group. Change the write mode to lock a group down, tighten retention for a sensitive workflow, or turn on redaction for a group that touches user data, all from Studio without rebuilding the agents themselves.
Key capabilities
- Wire any Studio surfaces — chat, apps, code, knowledge and data — into a single named memory group with a shared context
- Set retention policies per group so remembered items age out on your schedule instead of accumulating forever
- Control write mode per group — read-only, append-only or writable — to decide which surfaces can add to memory
- Apply PII redaction that strips personal data before it is written to the memory store
- Keep memory local-first on your device under BYOK, so policies apply where the data actually lives
Use cases
- Support lead: group a support chat with a customer data table, redact PII so agents recall the issue context without persisting names or emails
- Engineering manager: give a code-review agent a code-plus-knowledge memory group with append-only write mode so it builds context without overwriting docs
- Ops admin: set short retention on a group handling sensitive workflows so transient context clears out automatically instead of lingering
Frequently asked questions
What is a memory group in osFoundry Studio?
It is a named boundary that ties several surfaces — like a chat, an app, a code repo, a knowledge base or a data table — into one shared memory context. Agents working across those surfaces read and write to the same memory, governed by the group's retention, write-mode and PII-redaction policies.
How does PII redaction work with memory groups?
When redaction is enabled on a group, personal data is stripped before anything is written to the memory store, so agents can carry forward useful context without persisting identifiers like names or emails. Combined with osFoundry's local-first, bring-your-own-key model, the policy is applied where the memory actually lives rather than on a third-party server.
Can I control whether a surface can write to memory or only read from it?
Yes. Each memory group has a write mode, so you can make a group read-only, append-only, or fully writable. That lets you decide which surfaces are allowed to add new memories and which can only draw on existing context, without changing the agents themselves.