The outcome

Use the platform productively without giving it unnecessary access or authority.

Agno is a Agent platform formerly known as Phidata for Python agents, teams, workflows, memory, knowledge, evaluation, tracing, and AgentOS operations. Building Python agents, specialist teams, and deterministic workflows, then serving and managing them through AgentOS with sessions, memory, knowledge, tracing, evaluation, RBAC, and approvals. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Classify the task and its data before uploading or connecting anything.

  2. 02

    Review the current product, account, organization, retention, and training settings that apply to you.

  3. 03

    Grant the narrowest file, repository, workspace, microphone, screen, or integration permissions needed.

  4. 04

    Remove secrets and personal or regulated information unless your approved policy explicitly permits it.

  5. 05

    Review the output and revoke permissions or disconnect sources that are no longer needed.

Working standard

What good use looks like.

  • Phidata is the former name; current code and documentation use Agno and AgentOS, and older tutorials may reference removed or deprecated APIs. Persistent sessions, memory, knowledge, traces, callable caches, teams, and tools create privacy and cross-user risks. Bind state to authenticated identities, authorize tools independently, use narrow roles and approvals, pin versions, redact logs, cap loops and cost, and test migrations and deletion.
  • Follow your organization’s approved-use policy.
  • Never treat fluent output as authorization to act.

Phidata is the former name; current code and documentation use Agno and AgentOS, and older tutorials may reference removed or deprecated APIs. Persistent sessions, memory, knowledge, traces, callable caches, teams, and tools create privacy and cross-user risks. Bind state to authenticated identities, authorize tools independently, use narrow roles and approvals, pin versions, redact logs, cap loops and cost, and test migrations and deletion.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.