> ## Documentation Index
> Fetch the complete documentation index at: https://docs-dev.byterover.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# VS Code Extensions

> Connect ByteRover to Cline, GitHub Copilot, Kilo Code, and other VS Code coding agents

This guide covers connecting ByteRover to VS Code extension-based coding agents. Most extensions use **Skill** as the default connector for comprehensive project-level guidance, with **MCP** and **rules** as alternatives.

## Quick setup

<Tabs>
  <Tab title="TUI">
    Run `/connectors` in the interactive TUI, select your extension, and choose a connector type:

    ```
    /connectors
    ```
  </Tab>

  <Tab title="CLI">
    Install the default connector for your extension:

    ```bash theme={null}
    brv connectors install "Github Copilot"
    brv connectors install "Kilo Code"
    brv connectors install Cline
    ```

    Install a specific connector type with `--type` (or `-t`):

    ```bash theme={null}
    brv connectors install "Github Copilot" --type mcp
    brv connectors install Cline --type rules
    ```
  </Tab>
</Tabs>

***

## Cline

Cline uses **MCP** as the default connector, requiring manual configuration.

<Tabs>
  <Tab title="MCP (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Cline**
        3. Choose **MCP** connector
        4. Follow the **manual setup** instructions provided
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Cline
        ```
      </Tab>
    </Tabs>

    <Warning>
      Cline requires **manual MCP configuration**. ByteRover will display the configuration steps to follow.
    </Warning>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Cline**
        3. Choose **Rules** connector
        4. Done — Cline will read `.clinerules/agent-context.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Cline --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                          |
    | ------------------------ | ------------------------------ |
    | **Default connector**    | MCP                            |
    | **Supported connectors** | MCP, Rules                     |
    | Rule file                | `.clinerules/agent-context.md` |
    | MCP config               | Manual setup                   |
    | Auto-detected            | Yes                            |
  </Tab>
</Tabs>

***

## GitHub Copilot

GitHub Copilot uses **Skill** as the default connector for comprehensive project-level guidance.

<Tabs>
  <Tab title="Skill (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **GitHub Copilot**
        3. Choose **Skill** connector (recommended)
        4. ByteRover creates `.github/skills/byterover/` with:
           * `SKILL.md` — Quick reference with commands and best practices
           * `WORKFLOWS.md` — Detailed workflow patterns
           * `TROUBLESHOOTING.md` — Diagnostics and support info
        5. **Restart VS Code** to discover the skill files
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Github Copilot"
        ```

        <Tip>
          Install additional community agent skills from [BRV Hub](/brv-hub/overview):

          ```bash theme={null}
          brv hub install byterover-review --agent "Github Copilot"
          ```
        </Tip>
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="MCP">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **GitHub Copilot**
        3. Choose **MCP** connector
        4. ByteRover will configure `.vscode/mcp.json` automatically
        5. **Restart VS Code** to load the MCP server
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Github Copilot" --type mcp
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **GitHub Copilot**
        3. Choose **Rules** connector
        4. Done — Copilot will read `.github/copilot-instructions.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Github Copilot" --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                             |
    | ------------------------ | --------------------------------- |
    | **Default connector**    | Skill                             |
    | **Supported connectors** | Skill, MCP, Rules                 |
    | Skill directory          | `.github/skills/byterover/`       |
    | Rule file                | `.github/copilot-instructions.md` |
    | MCP config               | `.vscode/mcp.json` (auto-setup)   |
    | Auto-detected            | Yes                               |
  </Tab>
</Tabs>

***

## Kilo Code

Kilo Code uses **Skill** as the default connector for comprehensive project-level guidance.

<Tabs>
  <Tab title="Skill (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Kilo Code**
        3. Choose **Skill** connector (recommended)
        4. ByteRover creates `.kilocode/skills/byterover/` with:
           * `SKILL.md` — Quick reference with commands and best practices
           * `WORKFLOWS.md` — Detailed workflow patterns
           * `TROUBLESHOOTING.md` — Diagnostics and support info
        5. **Restart VS Code** to discover the skill files
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Kilo Code"
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="MCP">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Kilo Code**
        3. Choose **MCP** connector
        4. ByteRover will configure `.kilocode/mcp.json` automatically
        5. **Restart VS Code** to load the MCP server
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Kilo Code" --type mcp
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Kilo Code**
        3. Choose **Rules** connector
        4. Done — Kilo Code will read `.kilocode/rules/agent-context.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Kilo Code" --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                              |
    | ------------------------ | ---------------------------------- |
    | **Default connector**    | Skill                              |
    | **Supported connectors** | Skill, MCP, Rules                  |
    | Skill directory          | `.kilocode/skills/byterover/`      |
    | Rule file                | `.kilocode/rules/agent-context.md` |
    | MCP config               | `.kilocode/mcp.json` (auto-setup)  |
    | Auto-detected            | Yes                                |
  </Tab>
</Tabs>

***

## Roo Code

Roo Code uses **Skill** as the default connector for comprehensive project-level guidance.

<Tabs>
  <Tab title="Skill (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Roo Code**
        3. Choose **Skill** connector (recommended)
        4. ByteRover creates `.roo/skills/byterover/` with:
           * `SKILL.md` — Quick reference with commands and best practices
           * `WORKFLOWS.md` — Detailed workflow patterns
           * `TROUBLESHOOTING.md` — Diagnostics and support info
        5. **Restart VS Code** to discover the skill files
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Roo Code"
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="MCP">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Roo Code**
        3. Choose **MCP** connector
        4. ByteRover will configure `.roo/mcp.json` automatically
        5. **Restart VS Code** to load the MCP server
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Roo Code" --type mcp
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Roo Code**
        3. Choose **Rules** connector
        4. Done — Roo Code will read `.roo/rules/agent-context.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Roo Code" --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                         |
    | ------------------------ | ----------------------------- |
    | **Default connector**    | Skill                         |
    | **Supported connectors** | Skill, MCP, Rules             |
    | Skill directory          | `.roo/skills/byterover/`      |
    | Rule file                | `.roo/rules/agent-context.md` |
    | MCP config               | `.roo/mcp.json` (auto-setup)  |
    | Auto-detected            | Yes                           |
  </Tab>
</Tabs>

***

## Augment Code

Augment Code uses **MCP** as the default connector, requiring manual configuration.

<Tabs>
  <Tab title="MCP (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Augment Code**
        3. Choose **MCP** connector
        4. Follow the **manual setup** instructions provided
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Augment Code"
        ```
      </Tab>
    </Tabs>

    <Warning>
      Augment Code requires **manual MCP configuration**. ByteRover will display the configuration steps to follow.
    </Warning>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Augment Code**
        3. Choose **Rules** connector
        4. Done — Augment Code will read `.augment/rules/agent-context.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install "Augment Code" --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                             |
    | ------------------------ | --------------------------------- |
    | **Default connector**    | MCP                               |
    | **Supported connectors** | MCP, Rules                        |
    | Rule file                | `.augment/rules/agent-context.md` |
    | MCP config               | Manual setup                      |
    | Auto-detected            | Yes                               |
  </Tab>
</Tabs>

***

## Amp

Amp uses **Skill** as the default connector for comprehensive project-level guidance.

<Tabs>
  <Tab title="Skill (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Amp**
        3. Choose **Skill** connector (recommended)
        4. ByteRover creates `.agents/skills/byterover/` with:
           * `SKILL.md` — Quick reference with commands and best practices
           * `WORKFLOWS.md` — Detailed workflow patterns
           * `TROUBLESHOOTING.md` — Diagnostics and support info
        5. **Restart VS Code** to discover the skill files
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Amp
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="MCP">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Amp**
        3. Choose **MCP** connector
        4. ByteRover will configure `.vscode/settings.json` automatically
        5. **Restart VS Code** to load the MCP server
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Amp --type mcp
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Amp**
        3. Choose **Rules** connector
        4. Done — Amp will read `AGENTS.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Amp --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                                |
    | ------------------------ | ------------------------------------ |
    | **Default connector**    | Skill                                |
    | **Supported connectors** | Skill, MCP, Rules                    |
    | Skill directory          | `.agents/skills/byterover/`          |
    | Rule file                | `AGENTS.md`                          |
    | MCP config               | `.vscode/settings.json` (auto-setup) |
    | Auto-detected            | Yes                                  |
  </Tab>
</Tabs>

***

## Kiro

Kiro uses **Skill** as the default connector for comprehensive project-level guidance.

<Tabs>
  <Tab title="Skill (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Kiro**
        3. Choose **Skill** connector (recommended)
        4. ByteRover creates `.kiro/skills/byterover/` with:
           * `SKILL.md` — Quick reference with commands and best practices
           * `WORKFLOWS.md` — Detailed workflow patterns
           * `TROUBLESHOOTING.md` — Diagnostics and support info
        5. **Restart VS Code** to discover the skill files
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Kiro
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="MCP">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Kiro**
        3. Choose **MCP** connector
        4. ByteRover will configure `.kiro/settings/mcp.json` automatically
        5. **Restart VS Code** to load the MCP server
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Kiro --type mcp
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Kiro**
        3. Choose **Rules** connector
        4. Done — Kiro will read `.kiro/steering/agent-context.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Kiro --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                                  |
    | ------------------------ | -------------------------------------- |
    | **Default connector**    | Skill                                  |
    | **Supported connectors** | Skill, MCP, Rules                      |
    | Skill directory          | `.kiro/skills/byterover/`              |
    | Rule file                | `.kiro/steering/agent-context.md`      |
    | MCP config               | `.kiro/settings/mcp.json` (auto-setup) |
    | Auto-detected            | Yes                                    |
  </Tab>
</Tabs>

***

## Junie

Junie uses **Skill** as the default connector for comprehensive project-level guidance.

<Tabs>
  <Tab title="Skill (Default)">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Junie**
        3. Choose **Skill** connector (recommended)
        4. ByteRover creates `.junie/skills/byterover/` with:
           * `SKILL.md` — Quick reference with commands and best practices
           * `WORKFLOWS.md` — Detailed workflow patterns
           * `TROUBLESHOOTING.md` — Diagnostics and support info
        5. **Restart VS Code** to discover the skill files
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Junie
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="MCP">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Junie**
        3. Choose **MCP** connector
        4. ByteRover will configure `.junie/mcp/mcp.json` automatically
        5. **Restart VS Code** to load the MCP server
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Junie --type mcp
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Rules">
    <Tabs>
      <Tab title="TUI">
        1. Run `/connectors` in the ByteRover REPL
        2. Select **Junie**
        3. Choose **Rules** connector
        4. Done — Junie will read `.junie/guidelines.md` automatically
      </Tab>

      <Tab title="CLI">
        Install via the CLI:

        ```bash theme={null}
        brv connectors install Junie --type rules
        ```
      </Tab>
    </Tabs>
  </Tab>

  <Tab title="Details">
    | Property                 | Value                              |
    | ------------------------ | ---------------------------------- |
    | **Default connector**    | Skill                              |
    | **Supported connectors** | Skill, MCP, Rules                  |
    | Skill directory          | `.junie/skills/byterover/`         |
    | Rule file                | `.junie/guidelines.md`             |
    | MCP config               | `.junie/mcp/mcp.json` (auto-setup) |
    | Auto-detected            | Yes                                |
  </Tab>
</Tabs>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Curate Context" icon="sparkles" href="/common-workflows/curate-context">
    Learn how to add context to your knowledge base
  </Card>

  <Card title="Query Context" icon="search" href="/common-workflows/query-context">
    Retrieve context for your coding tasks
  </Card>
</CardGroup>