Teams

A team is a group of agents that share context and tools. Each agent in the team has its own role and instructions, but they share MCP servers, rate limits, and a common workspace.

Team Structure

rightplace/agents/my-team/
├── team.json                     # Team-level config
├── instructions/
│   └── instructions.md           # Shared context for all agents
├── agents/
│   ├── coder/
│   │   ├── agent.json            # Coder agent config
│   │   └── instructions.md       # Coder system prompt
│   ├── reviewer/
│   │   ├── agent.json            # Reviewer agent config
│   │   └── instructions.md       # Reviewer system prompt
│   └── writer/
│       ├── agent.json
│       └── instructions.md
└── sessions/
    └── ...

team.json

{
  "model": {
    "aiResourceId": "uuid",
    "modelId": "claude-sonnet-4-6"
  },
  "parameters": {
    "temperature": 0.7,
    "maxTokens": 4096
  },
  "mcpServers": [
    {
      "type": "resource",
      "resourceId": "uuid-of-shared-database"
    }
  ],
  "rateLimits": {
    "maxRequestsPerMinute": 30
  },
  "guardrails": {
    "maxTurns": 100
  }
}

How Teams Work

• Shared MCP servers — all agents in the team can access the same tools
• Shared rate limits — the team’s rate limit applies across all agents
• Individual instructions — each agent has its own system prompt and personality
• Model override — individual agents can use a different model than the team default
• Session context — chat sessions track which agent responded to each message

Using Teams in Chat

In the chat interface, you can switch between agents using the agent selector. You can also use @mention syntax to direct a message to a specific agent:

@reviewer Please review the code changes above

The chat history is shared across the session — all agents see previous messages regardless of which agent responded.

Creating a Team

1. Add an Agent resource to your project
2. Open it — the team structure is created automatically with a default “assistant” agent
3. Click the gear icon to configure the team
4. Add more agents by creating folders under agents/

Example: Development Team

Team instructions (instructions/instructions.md):

This team works on a Next.js e-commerce application.
Tech stack: Next.js 14, TypeScript, Prisma, PostgreSQL, Tailwind CSS.
Repository: github.com/company/store

Coder (agents/coder/instructions.md):

You write clean, tested code. Follow the project's existing patterns.
Always include TypeScript types. Write unit tests for new functions.

Reviewer (agents/reviewer/instructions.md):

You review code for bugs, security issues, and performance.
Be direct — point out the problem, explain why, suggest a fix.
Don't nitpick style issues.

Writer (agents/writer/instructions.md):

You write documentation and API docs.
Use clear, concise language. Include code examples.
Follow the project's existing doc style.