Run your team
Agent teams
Choose the right kind of agent
An agent is a worker using an AI account and model. A thread is its continuing conversation. Team members share the host workspace, configured connections and shared memory; give each a clear responsibility.
| Kind | Use it for | Where to continue |
|---|---|---|
| Chat | Interactive work and investigation | The same Chat conversation |
| Spawned agent | A bounded delegated task | Its separate Chat until the task is complete |
| Standing agent | An ongoing responsibility with optional scheduled triggers | Its persistent conversation |
| App agent | Maintaining a workflow and its interface | The App conversation |
Use Chat and Apps for interactive workflows and Schedules for recurring triggers.
Give a team a concrete outcome
- 1Define the work and limits
Specify the result, permitted actions, deadline and what needs your approval.
- 2Split independent responsibilities
Ask your lead agent to delegate bounded tasks, such as research and review, to separate agents. For shared files, assign distinct editing areas.
- 3Share the right context
Point workers at the same project files, shared memory or App records. Ask them to send findings and evidence back to the lead.
- 4Review and integrate
Have the lead collect results, resolve disagreements and validate the combined work before calling it complete. Delegation grants no new permissions; approval-gated tool actions still follow your configured approval policy.
Research three approaches to this problem. Delegate independent comparisons,
then have a separate agent review the evidence. Bring me one recommendation
with sources and unresolved questions. Do not buy anything or publish.Manage the team from laptop or phone
Use Kern's Chats, Spawned agents, Standing agents and Apps to open the relevant conversation and steer its work. The Swarm map shows relationships and recent involvement. Your AI subscription limits still constrain parallel work.
Set up remote HTTPS access to manage the same host from your phone. The host must remain running. A message being delivered is not proof that the recipient finished the task.