The outcome

Provide persistent assistance without cross-user memory leakage, unauthorized tools, or uncontrolled stored context.

Step by step

A workflow you can repeat.

  1. 01

    Define surfaces, users, tenants, agent role, data classes, model, knowledge, tools, session and memory policy, retention, approvals, SLO, budget, and audit ownership.

  2. 02

    Deploy AgentOS privately with authenticated routes, a production database, least-privilege service accounts, encrypted transport and storage, scoped secrets, and separate environments.

  3. 03

    Derive user and session IDs from verified identity, apply tenant filters to knowledge and state, register narrow tools with current authorization, and require approval for consequential effects.

  4. 04

    Test forged IDs, cross-tenant retrieval, memory poisoning, prompt injection, stale permissions, concurrent sessions, tool denial, model failure, database outage, deletion, and key rotation.

  5. 05

    Review traces and evals with redaction, monitor storage growth and cost, canary versions, audit roles and tools, and support user export, correction, memory reset, and deletion.

Working standard

What good use looks like.

  • Derive session identity server-side.
  • Filter all knowledge by tenant.
  • Support memory reset and deletion.

Official references

Check the current product documentation.