Skip to content

Create and Manage an Agent

Purpose

Create managed application content and find its Builder, deployments and evidence. External programs can use virtual keys without creating an Agent.

Prerequisites

An active Organization membership and agent.edit in one explicitly selected active Team. Reading uses agent.read; private tests use agent.test; publication uses separate deployment permissions.

Procedure

  1. Select a Team in the workspace header, then open Build → Agents → Create Agent. The list shows that Team's Agents with their status and an Open workspace link. If no Team is selected, use the page's Team selector and Select Team first. Enter the app name and optional description.
  2. Open Build to edit instructions, generation model and tools, save immutable snapshots and run a private Preview.
  3. Open Live to review and publish Production, change live access/accounts/limits, pause/resume, restore content or test the live version.
  4. Open Activity for authorized canonical Requests attributed to this Agent's deployments. This requires Team observability permission separately from Builder access.
  5. Open Settings to rename, describe or archive application content. Manage API credentials under Access → Virtual keys, not Agent Settings.

Expected result

Creating an Agent creates content only. It creates no Agent principal, reusable key or Production deployment. The workspace header retains the actual Team; All Teams is reporting/selection context, not a mutation target.

Verification

Create an Agent and confirm the tabs are Build, Live, Evaluate, Activity, Settings. Saving a draft does not alter Production. Switching to a different Team cannot silently mutate the original Agent.

Failure recovery

If a Team is absent or ambiguous, choose one explicitly. Missing model/tool choices require current catalog/Team allowance. Concurrent edits preserve local input; reload the latest draft in a separate view before reconciling. Old Agent key links direct you to virtual keys.