Visibility and scopes

Placement and visibility work together. Placement defines ownership; visibility defines the audience.

Visibility levels#

Personal agents support private and public visibility. Internal visibility requires an organization.

Installing a public source always creates a private installation in your destination scope. Installation visibility is fixed and cannot be selected or changed during the install flow. Choose an independent clone when you need to edit the bundle or choose a different visibility.

Team access is membership-based#

A team agent is available only when the caller's active team matches and the caller belongs to that team. Organization membership alone does not grant participation in a team agent.

Your active personal, organization, or team selection acts as a separate workspace identity. Private reads and management require that selection to exactly match the agent's placement; creating an organization agent does not make it manageable from your personal workspace. For organization agents without a team, the active organization and Better Auth permissions determine access. Public agents remain readable and installable regardless of scope, but their conversations and management sections remain private.

Scope controls configuration and billing#

Team agents resolve team configuration, organization agents resolve organization configuration, and personal agents resolve the creator's personal configuration. There is no fallback between scopes.

Personal usage is billed to the user. Organization and team agent usage is billed to the organization; the team is attribution, not a separate billing account.