Agent Configuration

Agents are AI employees on TeamDay — specialized team members you install, start with, or create for specific roles. This guide covers the settings available when configuring an agent.

Configuration depends on the agent type:

• Ready Agents: configure credentials, context, scope, schedule, and approvals. Teamday manages the global prompt, rubric, and upgrades.
• Teamday Agents: chat with them and grant local context. Teamday manages their core identity and behavior.
• Private Agents: fully editable agents owned by your organization.

Agent Fields

Private Agents have the following configurable fields. Ready Agents and Teamday Agents expose only the fields that are safe for their mutability level.

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:

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.

{
  "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 for how to build and manage skills.

Browser Computer is a built-in hosted runner skill for web browsing with a persistent browser profile. Use it when an agent needs screenshots, JavaScript-heavy pages, or authenticated website workflows. See Browser Computer.

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.

{
  "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 for available integrations.

Subagents

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

{
  "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

Models

Available Models

TeamDay supports models from multiple providers:

Claude (Anthropic):

Gemini (Google):

Teamday only lists Gemini CLI models that have passed a local headless CLI smoke for the current auth path. Antigravity CLI is exposed separately as antigravity-default because agy controls model choice through the connected Google account and does not currently expose a stable --model flag.

OpenAI:

Setting the Model

CLI:

teamday agents create --name "Fast Bot" --model claude-haiku-4-5-20251001 --system-prompt "..."

API:

{
  "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).

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

For Private Agents, the systemPrompt field is the core of your agent's behavior. Ready Agents and Teamday Agents have Teamday-managed core prompts; configure their local context and credentials instead of rewriting their identity.

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:

See Platform Tools for detailed documentation.

Updating Configuration

Private Agent fields can be updated after creation. Ready Agents and Teamday Agents reject protected prompt, identity, rubric, and tool-policy edits.

CLI:

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

API:

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. Protected Teamday-managed fields return an authorization error instead of mutating the agent product.

Next Steps

• Prompts & Instructions — Write better system prompts
• Tools — Deep dive into available tools
• Browser Computer — Give agents a persistent hosted browser
• Skills — Build and install reusable capabilities
• Spaces — Configure workspaces for your agents