Skip to content

Groups

A group is a shared configuration container for agents. Agents in the same group inherit the group’s provider keys, default model, and tool policies.


What Groups Control

SettingDescription
LLM provider keyThe API key used for LLM calls in group agents. Takes precedence over workspace-level secrets.
Default modelFallback model for agents that don’t specify one
Tool policiesAllowed / denied server-side tools for all agents in the group
Budget limitsToken and cost caps applied to every execution in the group

Key Resolution Order

When an agent executes, the intelligence layer resolves the provider key in this order:

  1. Group config (if the agent belongs to a group)
  2. Workspace secret
  3. 401 Unauthorized — no key found

Use Cases

Multi-product workspace: Use separate groups for each product line with different provider quotas and budget limits.

Cost isolation: Assign group-level budget caps to prevent a single agent from consuming the workspace’s entire credit allocation.

Key rotation: Update the provider key in one group config rather than on each individual agent.


Assigning Agents to Groups

Assign an agent to a group in the admin UI under the agent’s settings panel. An agent can belong to at most one group.