🐼 Berko Multi-Agent Extension
Build AI agent teams that collaborate on complex tasks using GitHub Copilot
🎯 What is Berko?
Berko is a VS Code extension that lets you create teams of AI agents that work together on your tasks. Instead of chatting with a single AI, you can:
- 🏗️ Create specialized agents (Frontend Dev, Backend Dev, QA, Tech Lead, etc.)
- 🤝 Watch them collaborate - agents can mention and delegate to each other
- 💬 Join the conversation - type messages anytime during agent discussions
- 📝 Persist context - each conversation remembers its history
- 📋 Define team rules - each team can have its own set of shared rules
⚡ One-Time Setup (5 minutes)
Before using Berko, you need to install and authenticate the GitHub Copilot CLI.
Prerequisites:
Step 1: Install GitHub Copilot CLI
Open VS Code's integrated terminal (`Ctrl+``) and run:
npm install -g @github/copilot
⚠️ Important: Install from VS Code's terminal to ensure it works immediately. Installing from external terminals may require a VS Code restart.
Step 2: Authenticate with GitHub
In the same VS Code terminal:
copilot
Once the CLI starts, type:
/login
Follow the browser authentication flow to connect your GitHub account.
Step 3: Verify Installation
copilot --version
If you see a version number, you're ready to go! 🎉
That's it! This is a one-time setup. Once installed and authenticated, Berko works across all your VS Code workspaces.
🚀 Quick Start
Step 1: Create Your First Team
- Open VS Code in any workspace
- Click the Berko panda icon 🐼 in the sidebar
- Click "+ Team" to create a new team
- Enter a name (e.g., "Development Team")
Step 2: Add Agents to Your Team
- Expand your team in the sidebar
- Click "+ Add Agent"
- Enter agent names like "Senior Developer", "Junior Developer", "QA Engineer"
- Each agent opens for editing - customize their role and skills
Step 3: Start Chatting!
- Click on a team to select all its agents
- Type a message and press Send
- Watch the agents initialize and respond
- Use @AgentName to mention specific agents
Example: Multi-Agent Collaboration
📖 Features
🧑🤝🧑 Team-Based Organization
Create multiple teams for different projects or workflows:
- Development Team (Frontend, Backend, DevOps)
- Design Team (UX Designer, UI Designer, Researcher)
- Review Team (Code Reviewer, Security Auditor, QA)
📋 Team Rules
Each team can have its own shared rules that all agents follow. Edit team rules via the context menu (right-click on team → Edit Team Rules).
Team rules are stored in .system/TeamRules.md inside each team folder. Example:
# Team Rules
## Communication Guidelines
- Always be concise and clear
- Use code blocks for any code snippets
- Mention teammates with @Name when delegating
## Workflow Rules
- Junior developers should ask Senior for code review
- QA should test all code before marking complete
- All changes must include documentation updates
## Code Standards
- Follow TypeScript best practices
- Use meaningful variable names
- Add comments for complex logic
💬 Multi-Agent Conversations
Agents collaborate through @mentions:
- You send a message → Agent responds
- Agent mentions @Teammate → Message is routed to that teammate
- Multiple agents can work in parallel when mentioned together
- The conversation flows like a real team discussion
Example: @Senior and @Junior implement login - both agents work simultaneously!
📂 Conversation History
- Switch between multiple conversations
- Each conversation maintains separate context
- Resume previous conversations with full memory
🎨 Model Selection
Choose from multiple AI models:
- Claude Opus 4.5 (default)
- Claude Sonnet 4
- GPT-4o
- And more...
⚙️ Customizable Agents
Each agent has:
- Name & Description - Who they are
- Role & Skills - What they're good at
- System Prompt - How they behave
- Response Style - How they communicate
🛠️ Agent Configuration
Agents are defined in JSON files with this structure:
{
"$schema": "../agent-card.schema.json",
"name": "SeniorDev",
"displayName": "Senior Developer",
"description": "Experienced developer who mentors juniors",
"role": "Lead Developer",
"skills": ["architecture", "code-review", "mentoring"],
"responseStyle": "professional",
"systemPrompt": "You are a senior developer with 10+ years of experience..."
}
Agent Properties
| Property |
Description |
name |
Unique identifier (used for @mentions) |
displayName |
Friendly name shown in UI |
description |
Brief description of the agent |
role |
Job title or function |
skills |
Array of capabilities |
responseStyle |
casual, professional, technical |
systemPrompt |
Detailed instructions for the AI |
🗂️ File Structure
your-workspace/
├── agents/ # Agent teams folder
│ ├── YourTeam/ # Team folder
│ │ ├── .team.json # Team configuration
│ │ ├── Agent1.agent.json # Agent definition
│ │ ├── Agent2.agent.json # Agent definition
│ │ └── .system/ # System files
│ │ └── TeamRules.md # Shared team rules
│ └── AnotherTeam/
│ └── ...
├── .berko-sessions/ # Session persistence (auto-generated)
└── .berko-conversations/ # Chat history (auto-generated)
⌨️ Commands
| Command |
Description |
Berko: Open Chat |
Open the Berko chat panel |
On Teams:
- 📝 Edit Team Rules - Open the shared rules file
- 🧹 Clear Sessions - Reset all agent memory in this team
- 🗑️ Delete Team - Remove the team and all its agents
On Agents:
- 📝 Edit Agent - Open the agent configuration file
- 🧹 Clear Session - Reset this agent's memory
- 🗑️ Delete Agent - Remove the agent
💡 Tips & Tricks
Use @mentions for Directed Tasks
@Junior please implement the login form
@Senior please review @Junior's implementation
Create Workflow Chains
@Designer create mockups for dashboard, then @Frontend implement them
Leverage Specialists
Create agents with specific expertise:
- Database Expert - SQL optimization, schema design
- Security Auditor - vulnerability scanning, best practices
- Performance Engineer - profiling, optimization
Set Up Team Rules for Consistency
Define team-wide standards in TeamRules.md:
- Code formatting preferences
- Review processes
- Communication guidelines
- Project-specific conventions
🔧 Settings
Access via VS Code Settings > Extensions > Berko:
| Setting |
Default |
Description |
berko.maxIterations |
50 |
Max back-and-forth before pausing |
🐛 Troubleshooting
"Copilot CLI not found"
- Open VS Code's integrated terminal (`Ctrl+``)
- Run:
npm install -g @github/copilot
- Verify:
copilot --version
If you installed from an external terminal, restart VS Code completely.
- Open VS Code terminal
- Run:
copilot
- Type:
/login
- Complete the browser authentication
Agents not responding
- Check if CLI is working:
copilot --version (in VS Code terminal)
- Check if authenticated:
copilot then /status
- Clear agent sessions (right-click on agent → Clear Session)
- Restart VS Code
Slow initialization
First-time agent initialization takes ~30-60 seconds as it establishes sessions. Subsequent messages are faster.
📋 Requirements Summary
| Requirement |
Version |
Notes |
| VS Code |
1.85+ |
Required |
| Node.js |
18+ |
Required for npm install |
| GitHub Copilot CLI |
Latest |
npm install -g @github/copilot |
| GitHub Copilot Subscription |
Active |
Required for CLI |
🤝 Contributing
🚧 Coming Soon! This project will be open-sourced and ready for contributions. Stay tuned!
📄 License
MIT License - See LICENSE for details
Happy collaborating with your AI team! 🐼