> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/quickstart-guides/github-copilot-guide.md).

# Connect GitHub Copilot to Snyk

How to set up Snyk Studio in GitHub Copilot with the Snyk CLI

Set up Snyk Studio in GitHub Copilot to scan code and dependencies, evaluate package health, and fix vulnerabilities from your coding assistant.

For enterprise deployment across your development teams, use the [Agentic Development Security (ADS) installer](/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment.md). The following procedure is for local developer setup.

## Install Snyk Studio with hooks support

Install GitHub Copilot and the [Snyk CLI](https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli). Enable the Snyk products you want to scan with. Complete the account and product setup in [Getting started with Snyk Studio](/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md).

1. Authenticate with Snyk:

   ```bash
   snyk auth
   ```
2. Run the installer as the developer who uses GitHub Copilot:

   ```bash
   snyk studio install --experimental --ade=copilot-cli,copilot-vscode
   ```
3. Start a new session in GitHub Copilot and open the repository you want to work in. Complete any MCP authentication or folder-trust request.

The example configures both Copilot CLI and Copilot in VS Code. Use `--ade=copilot-cli` or `--ade=copilot-vscode` to configure only one of them. This setup does not require the legacy Studio opt-in in the Snyk IDE extension.

## Verify installation

Run:

```bash
snyk studio install --experimental --verify --ade=copilot-cli,copilot-vscode
```

This checks the installed assets. For merged configuration files, the verifier checks only file existence. It does not confirm that a scan completed.

Ask GitHub Copilot to scan the repository:

```
Scan this repository for code and dependency vulnerabilities. Summarize the findings before making changes.
```

## Check background hook scanning

Run a coding task in a new assistant session. Studio hooks trigger background scans for supported code and dependency changes. Inspect the activity with:

```bash
snyk studio logs --experimental --level=debug
```

Check for hook events and scan results. A successful direct MCP scan does not verify that the hooks ran. For scan failures, authentication, or missing activity, visit [Troubleshooting](/agent-security/agentic-security-with-snyk-studio/troubleshooting.md).

## Use remediation

Codex and GitHub Copilot CLI receive the Snyk Fix skill. Ask the assistant to use that skill for existing vulnerabilities. Other installed assistant components use their command or workflow mechanism. Visit [Remediation directives](/agent-security/agentic-security-with-snyk-studio/directives.md#remediation-directives) for the differences.

## Update or remove Snyk Studio

After updating the Snyk CLI, run the installation command again to refresh the components, then start a new assistant session.

To remove the local setup for GitHub Copilot, run:

```bash
snyk studio install --experimental --uninstall --ade=copilot-cli,copilot-vscode
```

If your company deployed Studio through ADS, use the [ADS removal procedure](/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment.md#uninstall).

## Manual MCP configuration

For an MCP-only connection, use the [manual configuration instructions](/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md#configure-the-snyk-mcp-server) with your client's supported configuration format. Manual MCP setup does not install the full Studio components.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/quickstart-guides/github-copilot-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.