Creating Your First Studio
A Studio is a self-contained delivery environment with its own members, agents, context, policies and audit trail. Creating one takes a few minutes; the decisions below are the ones worth pausing on.
Create the Studio
From Manage Studios, choose Create Studio and give it a name and a one-line purpose. If your account belongs to an Organisation you can attach the Studio to it now, so it inherits branding, users and billing.
Pick a trust level
Trust Settings decides how much an agent may do before a human intervenes — from proposing a plan only, through to running verified changes end to end. Start conservative; you can raise it once you have seen the agents work.
Configure a model provider
Model Config is where you connect an AI provider. Keys are encrypted with a dedicated AWS KMS key, stored server-side and never reach the browser — test the connection from this page rather than pasting a key anywhere else.
Seed the Context Library
Agents ground their work in the Context Library. Add your product brief, architecture notes, coding standards and anything else an agent should treat as fact. Thin context is the most common cause of disappointing runs.
Assemble the hybrid team
Add people under Humans and choose agents from the Agent Roster. Agent Recruitment walks you through picking agent types for the work you expect.
Set policies and checklists
Policies and DoR & DoD define what a work package must satisfy before it starts and before it is accepted. These are enforced at the gates, so they are worth getting right early.