Create a new agent

Spin up a custom agent — a specialist your project actually needs — in a few minutes, without writing any code.

The default roster gets most projects most of the way, but every project eventually wants a specialist that doesn’t exist yet: a data engineer, a security reviewer, a content writer, a copy editor. Custom agents fill that gap.

Where to start

Open the project sidebar and click Agents. At the bottom of the roster you’ll see + New agent. The creation flow is a wizard with four steps.

Identity

Give the agent a name, a slug (used in @mentions), and an avatar. Pick a colour for the working ring.

Role & reporting line

Describe what they do in two or three sentences, and choose who they report to. The reporting line determines how routing works — if they report to a principal, the principal can hand them tickets.

Identity files

The Studio drafts a starter AGENTS.md and SOUL.md based on what you typed. Edit them inline. You’ll almost always want to tighten the Definition of Done and add a tech-stack section if they touch code.

Skills

Pick the skills they should have access to. Most agents want studio-app and one or two domain skills. A code-writing agent will also want gh-cli and an editor-relevant skill (frontend-design, backend-conventions, etc.).

Test before you trust

Before you put the new agent on a real ticket, give them a small one — a doc update, a copy change, a tiny refactor. Watch how they scope it, what tools they reach for, what they ask before acting. Adjust the identity file based on what you see.

Sharing agents across projects

Custom agents are project-scoped by default. If you want the same agent in another project, open the agent’s profile and click Promote to org. Org agents are available to every project in the workspace.