Skip to main content
This guide covers connecting ByteRover to VS Code extension-based coding agents. Most extensions use MCP as the default connector for direct tool integration, with rules as a fallback option.

Quick Setup

For all VS Code extensions, the setup is the same:
brv           # Start REPL mode
/connectors   # Launch connector manager
Select your extension, choose your connector type (MCP recommended, or Rules as fallback), and the configuration will be created automatically.

Cline

Cline uses MCP as the default connector, requiring manual configuration.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select Cline
  4. Choose MCP connector
  5. Follow the manual setup instructions provided
Cline requires manual MCP configuration. ByteRover will display the configuration steps to follow.

GitHub Copilot

GitHub Copilot uses MCP as the default connector for direct tool integration, with skill and rules as alternatives.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select GitHub Copilot
  4. Choose MCP connector
  5. ByteRover will configure .vscode/mcp.json automatically
  6. Restart VS Code to load the MCP server

Kilo Code

Kilo Code uses MCP as the default connector for direct tool integration.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select Kilo Code
  4. Choose MCP connector
  5. ByteRover will configure .kilocode/mcp.json automatically
  6. Restart VS Code to load the MCP server

Roo Code

Roo Code uses MCP as the default connector for direct tool integration.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select Roo Code
  4. Choose MCP connector
  5. ByteRover will configure .roo/mcp.json automatically
  6. Restart VS Code to load the MCP server

Augment Code

Augment Code uses MCP as the default connector, requiring manual configuration.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select Augment Code
  4. Choose MCP connector
  5. Follow the manual setup instructions provided
Augment Code requires manual MCP configuration. ByteRover will display the configuration steps to follow.

Amp

Amp uses MCP as the default connector for direct tool integration.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select Amp
  4. Choose MCP connector
  5. ByteRover will configure .vscode/settings.json automatically
  6. Restart VS Code to load the MCP server

Kiro

Kiro uses MCP as the default connector for direct tool integration.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select Kiro
  4. Choose MCP connector
  5. ByteRover will configure .kiro/settings/mcp.json automatically
  6. Restart VS Code to load the MCP server

Junie

Junie uses MCP as the default connector for direct tool integration.
  1. Start the ByteRover REPL: brv
  2. Run /connectors
  3. Select Junie
  4. Choose MCP connector
  5. ByteRover will configure .junie/mcp/mcp.json automatically
  6. Restart VS Code to load the MCP server

Next Steps