# Agent Configuration

Configure AI agents — models, equipment (tools, skills, MCPs, subagents), visibility, and system prompts.

# Agent Configuration

Agents are AI employees on TeamDay — specialized team members you hire and equip for specific roles. This guide covers all the settings available when configuring an agent.

---

## Agent Fields

Every agent has the following configurable fields:

| Field | Required | Description |
|-------|----------|-------------|
| `name` | Yes | Display name |
| `systemPrompt` | Yes | System prompt — the core instructions that define behavior |
| `role` | No | Role description (default: "Assistant") |
| `model` | No | AI model ID (default: `claude-sonnet-4-6`) |
| `category` | No | `marketing`, `finance`, `hr`, `engineering`, `operations`, `general`, `data` |
| `visibility` | No | `private`, `organization`, `public`, `unlisted` (default: `organization`) |
| `skillIds` | No | Skills attached to this agent (e.g., `["core:research-assistant"]`) |
| `mcpInstanceIds` | No | MCP integrations attached to this agent |
| `subagentIds` | No | Other agents this agent can delegate work to |
| `allowedTools` | No | Tool allowlist (default: all tools enabled) |
| `disabledTools` | No | Tools to disable (alternative to allowlist) |
| `tags` | No | Tags for organization and filtering |
| `description` | No | Short description (up to 500 chars) |
| `initialGreeting` | No | First message when a user starts a chat |
| `image` | No | Avatar image URL |
| `slug` | No | URL slug for public marketing page |
| `longDescription` | No | Extended description for marketing page |
| `useCases` | No | List of use case descriptions |
| `faq` | No | FAQ items (`[{question, answer}]`) |
| `integrations` | No | List of integration names |
| `seo` | No | SEO metadata (`{title, description, keywords}`) |

---

## Equipment

Agents have four types of equipment, each managed via a dedicated tab in the agent detail panel:

### Tools

Built-in Claude tools that every agent has access to by default:

| Tool | Description |
|------|-------------|
| `Read` | Read files from the workspace |
| `Write` | Write files to the workspace |
| `Edit` | Make targeted edits to existing files |
| `Bash` | Run shell commands |
| `Glob` | Find files by pattern |
| `Grep` | Search file contents |
| `WebSearch` | Search the web |
| `WebFetch` | Fetch and process web pages |
| `Task` | Launch subagents for complex tasks |
| `SendMessage` | Communicate between agents |
| `Skill` | Invoke skills as slash commands |

Tools are universal — the same set is available whether the agent is chatting at org level or in a space. Use `disabledTools` to restrict specific tools, or `allowedTools` to set an explicit allowlist.

### Skills

Reusable capabilities attached to the agent via `skillIds`. Skills provide domain expertise, workflows, and automation scripts.

```json
{
  "skillIds": ["core:research-assistant", "core:data-analyst"]
}
```

Skills can also be attached to a space (via `skillRefs`). When an agent chats in a space, it gets the **union** of its own skills and the space's skills. When chatting at org level, it only gets its own skills.

See [Skills](https://docs.teamday.ai/guides/skills) for how to build and manage skills.

### MCPs

External integrations attached to the agent via `mcpInstanceIds`. MCP (Model Context Protocol) servers connect agents to external services like Google Analytics, GitHub, Slack, etc.

```json
{
  "mcpInstanceIds": ["mcp-instance-id-1", "mcp-instance-id-2"]
}
```

MCPs can also be installed on a space. When an agent chats in a space, it gets the **union** of its own MCPs and the space's MCPs. At org level, it only gets its own MCPs.

See [MCP Servers](https://docs.teamday.ai/guides/mcp-servers/what-are-mcp-servers) for available integrations.

### Subagents

Other agents this agent can delegate work to, attached via `subagentIds`. Subagents run isolated tasks and report results back.

```json
{
  "subagentIds": ["agent-id-1", "agent-id-2"]
}
```

Subagents can also be defined as markdown files in a space's `.claude/agents/` directory. The agent discovers both its configured subagents and any filesystem-based subagents in the space.

### Equipment Scope: Org Chat vs Space Chat

| Context | Equipment Available |
|---------|-------------------|
| **Org-level chat** | Agent's own equipment only (its tools, skills, MCPs, subagents) |
| **Space chat** | Agent's equipment **union** space's resources (skills, MCPs, subagents from filesystem) |

---

## Models

### Available Models

TeamDay supports models from multiple providers:

**Claude (Anthropic):**

| Model ID | Name | Description | Pricing (per 1M tokens) |
|----------|------|-------------|------------------------|
| `claude-sonnet-4-6` | Claude Sonnet 4.6 | Best value — fast, smart, great for coding | $3 in / $15 out |
| `claude-opus-4-6` | Claude Opus 4.6 | Most capable — complex reasoning | $5 in / $25 out |
| `claude-haiku-4-5-20251001` | Claude Haiku 4.5 | Fastest — simple tasks | $1 in / $5 out |

**Gemini (Google):**

| Model ID | Name | Pricing (per 1M tokens) |
|----------|------|------------------------|
| `gemini-3-pro-preview` | Gemini 3 Pro (Preview) (coming soon) | $2 in / $12 out |
| `gemini-3-flash-preview` | Gemini 3 Flash (Preview) (coming soon) | $0.50 in / $3 out |
| `gemini-2.5-pro` | Gemini 2.5 Pro | $1.25 in / $10 out |
| `gemini-2.5-flash` | Gemini 2.5 Flash | $0.30 in / $2.50 out |

**OpenAI:**

| Model ID | Name | Pricing (per 1M tokens) |
|----------|------|------------------------|
| `gpt-5.3-codex-2026-02-05` | GPT-5.3 Codex (coming soon) | $1.75 in / $14 out |
| `gpt-5.1-2025-11-13` | GPT-5.1 (coming soon) | $1.25 in / $10 out |
| `gpt-5-mini` | GPT-5 Mini (coming soon) | $0.25 in / $2 out |

### Setting the Model

**CLI:**
```bash
teamday agents create --name "Fast Bot" --model claude-haiku-4-5-20251001 --system-prompt "..."
```

**API:**
```json
{
  "name": "Fast Bot",
  "model": "claude-haiku-4-5-20251001",
  "systemPrompt": "..."
}
```

---

## Visibility

Visibility controls who can **discover** your agent. It does not control where the agent is used — that's determined by attachment (adding the agent to a space or starting a chat).

| Level | Description |
|-------|-------------|
| `private` | Only the creator can see and use |
| `organization` | All members of your organization **(default)** |
| `public` | Listed on the TeamDay `/team` page — anyone can use |
| `unlisted` | Accessible via direct link, not listed publicly |

Public agents get a marketing page at `teamday.ai/team/{slug}` with their description, FAQ, use cases, and a "Add to Team" button.

---

## System Prompt

The `systemPrompt` field is the core of your agent's behavior. See [Prompts & Instructions](https://docs.teamday.ai/guides/prompts-instructions) for a complete guide.

Key tips:
- Start with identity: "You are [Name], a [role]"
- Define behavior: what the agent should do and how
- Set constraints: what the agent should not do
- Be specific: vague prompts produce vague results

---

## Platform MCP Tools

TeamDay provides built-in MCP tools that all agents can use:

| Tool | Purpose |
|------|---------|
| `mcp__teamday-media__MediaGeneration` | Generate images and videos |
| `mcp__teamday-admin__TeamdayAdmin` | Manage platform resources (spaces, agents, skills) |
| `mcp__teamday-ui__UICommand` | Control the chat interface (notifications, modals, handoffs) |

See [Platform Tools](https://docs.teamday.ai/guides/platform-tools/media-generation) for detailed documentation.

---

## Updating Configuration

All fields can be updated after creation:

**CLI:**
```bash
teamday agents update <id> --model claude-opus-4-6 --system-prompt "New instructions..."
teamday agents update <id> --skills "core:research-assistant,new-skill"
```

**API:**
```bash
curl -X PATCH "https://cc.teamday.ai/api/v1/agents/<id>" \
  -H "Authorization: Bearer $TEAMDAY_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"model": "claude-opus-4-6"}'
```

Only provided fields are updated. Omitted fields remain unchanged.

---

## Next Steps

- [Prompts & Instructions](https://docs.teamday.ai/guides/prompts-instructions) — Write better system prompts
- [Tools](https://docs.teamday.ai/guides/tools) — Deep dive into available tools
- [Skills](https://docs.teamday.ai/guides/skills) — Build and install reusable capabilities
- [Spaces](https://docs.teamday.ai/guides/spaces) — Configure workspaces for your agents