AI Bot Teams
Why Bot Teams?
When you use Claude Code with VibeCodes, all actions show up as "Claude Code" in your activity log, comments, and task assignments. That works fine for a single session — but what if you want to run multiple Claude Code sessions in parallel, each working on different tasks?
Bot teams solve this. You create distinct bot personas — like "Dev Alpha", "QA Tester", or "UX Scout" — each with its own name, role, and system prompt. When a Claude Code session operates as a bot, all its actions are attributed to that specific bot. You can see exactly which AI agent did what.
Creating Bots
Bots are managed on your profile page. Scroll to the "My Bots" section:
- Click Create Bot
- Enter a name (e.g., "Dev Alpha")
- Pick a role template — Developer, UX Designer, Business Analyst, QA Tester, Product Owner, Automated Tester, DevOps, or Support — or leave it blank for a general-purpose bot
- Customize the system prompt if you want. This prompt is stored on the bot and available to Claude Code via the
get_bot_prompttool - Click Create
Your bots are global — they work across all your ideas, not just one. Create them once, use them everywhere.
Role Templates
VibeCodes includes eight role templates with pre-written system prompts. Each template comes with a structured prompt (goal, constraints, and approach) that you can customise. Pick one as a starting point, then edit to match your needs:
Developer
Focuses on clean, tested code. Follows existing patterns. Flags architectural concerns.
UX Designer
Reviews for usability and accessibility. Checks WCAG compliance. Suggests UI improvements.
Business Analyst
Reviews requirements for completeness. Writes acceptance criteria. Breaks vague tasks into actionable subtasks.
QA Tester
Reviews completed tasks for bugs. Writes test scenarios. Reports issues with reproduction steps.
Product Owner
Prioritises backlog by user impact. Writes user stories. Communicates trade-offs to stakeholders.
Automated Tester
Writes and maintains automated tests. Tracks coverage. Catches regressions early.
DevOps
Manages CI/CD pipelines. Automates deployments. Keeps environments consistent and monitored.
Support
Triages user-reported issues. Reproduces bugs. Escalates with clear reproduction steps and severity.
Structured Prompt Builder
When creating or editing a bot, the prompt builder helps you craft effective system prompts using three structured fields:
- Goal — what the bot should achieve (e.g., "Deliver production-ready code that follows project conventions")
- Constraints — what the bot must never do (e.g., "Ship code without tests")
- Approach — how the bot should work (e.g., "Read existing code before writing new code")
Role templates pre-fill these fields. You can edit them or switch to a freeform text prompt at any time. The builder combines the fields into a single system prompt that Claude follows when acting as that bot.
Assigning Bots to Tasks
On any kanban board, open a task and look for the assignee dropdown. Your active bots appear in a "My Bots" section below the team members, marked with a bot icon.
When you assign a bot to a task, VibeCodes automatically adds it as a collaborator on the idea. This ensures the bot has the right permissions to work on the board.
Using Bots with Claude Code
Start Claude Code normally with the VibeCodes MCP server connected, then ask it to switch identity using the set_bot_identity tool:
"Switch to my Dev Alpha bot and check what tasks are assigned to it""Set identity to QA Tester and review completed tasks on the board"Once identity is set, three things happen automatically:
- All actions (comments, task updates, activity log entries) are attributed to that bot
- If the bot has a system prompt, Claude automatically adopts the persona — no need to manually tell it to follow the prompt
- The identity is persisted to the database — it survives reconnections, restarts, and new sessions. No need to re-set identity each time.
To reset back to the default identity, just say "Reset bot identity" and Claude will stop following the bot persona. The reset is also persisted.
Example: Parallel Development
Here's a typical workflow with two bots working in parallel:
- Create two bots on your profile: "Dev Alpha" (Developer role) and "QA Scout" (QA Tester role)
- Assign tasks on your board: drag "Build login page" to Dev Alpha, drag "Write test plan" to QA Scout
- Open two terminal windows and start Claude Code in each
- In terminal 1:
"Switch to Dev Alpha and work on my assigned tasks" - In terminal 2:
"Switch to QA Scout and work on my assigned tasks" - Watch the board update in real-time as both bots work. Each bot's comments and activity entries show its own name and bot icon.
Bot MCP Tools
These tools are available when connected via MCP:
| Tool | Description |
|---|---|
| list_bots | List all bots you own, with name, role, and active status |
| set_bot_identity | Switch to a specific bot (by name or ID). Identity is persisted across sessions. Call with no args to reset. |
| get_bot_prompt | Retrieve the system prompt for the active bot — Claude Code can read this to know how to behave |
| create_bot | Create a new bot directly from Claude Code (name, role, system prompt) |
How Bots Appear in the UI
Bots are distinguished from human users throughout the board:
- Task cards — bot assignees show a small bot icon overlay on their avatar
- Activity timeline — bot actions show a bot icon next to the actor name
- Task comments — bot comments show a bot icon next to the author name
- Assignee dropdown — bots appear in a separate "My Bots" section with bot icons
Managing Bots
On your profile page, you can:
- Edit a bot's name, role, system prompt, or avatar
- Deactivate a bot (toggle the active switch) — deactivated bots won't appear in the assignee dropdown but their historical activity is preserved
- Delete a bot — this removes it permanently. The default "Claude Code" bot cannot be deleted.