> 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.md).

# Quickstart guides

Quickstart guides for setting up Snyk Studio with common AI coding assistants

Choose the setup for your coding assistant. For local developer setup, the [Studio CLI installer](/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md#install-on-your-machine) configures supported components together. For enterprise rollout, use the [Agentic Development Security (ADS) installer](/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment.md).

## Assistants configured by the Studio installer

| Assistant                              | Setup guide                                                                                                                   |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Claude Code                            | [Connect Claude Code to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/claude-code-guide.md)       |
| Cursor                                 | [Connect Cursor to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/cursor-guide.md)                 |
| Codex                                  | [Connect Codex to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/codex-cli-guide.md)               |
| Gemini CLI (access restrictions apply) | [Connect Gemini CLI to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/gemini-cli-guide.md)         |
| GitHub Copilot CLI and VS Code         | [Connect GitHub Copilot to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/github-copilot-guide.md) |
| Kiro                                   | [Connect Kiro to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/kiro-guide.md)                     |

The installer configures MCP access and remediation and package-health components for all assistants in this table. Visit the [capability matrix](/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md#coding-assistant-support) to see which assistants also receive Secure at inception hooks.

Google is restricting access to Gemini CLI and Gemini Code Assist. Visit [Migrate from Gemini tooling](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/antigravity-guide.md#migrate-from-gemini-tooling) for the schedule and the Antigravity path. The `gemini` installer target does not configure Antigravity CLI.

The installer retains a legacy `windsurf` target for old Cascade configuration. For agent-invoked Snyk tools in Devin Local, use [Connect Devin Desktop to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/windsurf-guide.md). This manual integration does not install Studio hooks or skills.

## Import findings into Daybreak Defense Factory

Daybreak Defense Factory imports Snyk findings through the Codex Security CLI. The Studio installer does not configure it. For setup, visit [Connect Daybreak Defense Factory to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/daybreak-defense-factory-guide.md).

## Manual MCP integrations

These guides explain how to connect a client to the local Snyk MCP server:

* [Connect Amazon Q to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/amazon-q-guide.md)
* [Connect Antigravity to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/antigravity-guide.md)
* [Connect Augment Code to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/augment-code-guide.md)
* [Connect Cline to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/cline-guide.md)
* [Connect Continue to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/continue-guide.md)
* [Connect Devin to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/devin-guide.md)
* [Connect Devin Desktop to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/windsurf-guide.md)
* [Connect Factory to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/factory-guide.md)
* [Connect Factory Terminal/IDE to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/factory-terminal-ide-guide.md)
* [Connect Gemini Code Assist to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/gemini-code-assist-guide.md)
* [Connect Goose CLI to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/goose-cli-guide.md)
* [Connect JetBrains AI Assistant to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/jetbrains-ai-assistant.md)
* [Connect JetBrains Junie to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/jetbrains-junie.md)
* [Connect Qodo to Snyk](/agent-security/agentic-security-with-snyk-studio/quickstart-guides/qodo-guide.md)

A manual MCP connection gives the assistant access to Snyk tools. It does not install the Studio Secure at inception hooks. Rules instruct the assistant to scan, but depend on the model following those instructions.

If the connection fails, visit [Troubleshooting](/agent-security/agentic-security-with-snyk-studio/troubleshooting.md).


---

# 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.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.
