Skip to navigation
Sessions

Create and configure an agent

Save a coding agent, model, instructions and approval settings to reuse
View as Markdown

An agent is a saved setup for sessions: a coding agent, a model, standing instructions, how often it asks first, and an optional repository. You pick one each time you start a session.

Owners, Admins and Engineers can create, edit and archive agents. Other roles can see them.

Create an agent

1

Open the Agents tab

Open the project and choose the Agents tab, then New agent.

2

Name it and pick a coding agent

Enter a Name, then choose the Coding agent: Claude Code, Codex, Kiro (preview), Tower (preview), Cursor (preview) or Antigravity (preview).

3

Choose the code and model

Pick a Repository, or No repository. Leave Model on Default model, pick one from the list, or choose Custom model ID….

4

Write instructions

In Instructions, add what the agent should follow in every session, such as coding standards or how to test.

5

Set how it asks

Choose a Permission mode (see below), then choose Create agent.

New agent panel with Name, Coding agent, Repository, Model, Instructions and Permission mode filled in, and the Create agent button
The New agent form

Choose a permission mode

ModeWhat the agent does
Ask first (default)Asks before protected actions.
Auto editsEdits files without pausing.
Auto edits + shellAlso runs shell commands and searches and fetches from the web.
Full accessDoesn’t ask before editing files or running commands.

People can pick a different mode for one session when they start it.

Edit or archive an agent

On the agent’s row, choose Edit, change the settings, and choose Save changes. To retire it, choose Archive, then Archive in Archive {name}?.

Agents tab with a search box and a table of agents showing Name, Coding agent, Repository, Model and Status, with New session, Edit and Archive on each row
The Agents tab

Good to know

  • Edits apply to new sessions only. Running sessions keep the settings they started with.
  • The repository is set when you create the agent. For another repository, create another agent.
  • New session on a row opens the composer with that agent picked.
  • Archiving hides the agent from new sessions and can’t be undone. Its past sessions stay.
  • A row that says Relink required needs GitHub access again: choose Relink GitHub. See GitHub.
  • Claude Code agents also have Thinking (Default, Adaptive or Off) and Default effort in the edit form.
SettingWhat it does
Default AI accountChoose when a session starts, or an organization AI account to always use. Personal accounts are picked at session start. See Project AI accounts.
Sandbox resourcesPlan default, a size (Shrimp, Tuna, Shark or Whale), or Custom CPU and memory. Your plan decides which sizes you can use. See Sandboxes.
Spend limitLimit this agent’s spend caps what its sessions spend. Only Owners and Admins can change it.
Session token limitDefault token cap for new sessions: None, 500K, 1M, 2M or 5M. Not available for Kiro.