> 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/scan-fix-and-prevent/scan-with-snyk/snyk-secrets/secrets-scanning-in-the-ide.md).

# Secrets scanning in the IDE

Scan for exposed secrets in Visual Studio Code and JetBrains IDEs.

{% hint style="info" %}
Snyk Secrets supports Visual Studio Code, Visual Studio, JetBrains IDEs, and Eclipse.
{% endhint %}

Find exposed secrets as you work with Snyk Secrets in your IDE. Select your IDE for setup instructions and scan guidance.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><h3>Visual Studio Code</h3><p>Use the Snyk extension to scan for secrets in Visual Studio Code.</p><p><a href="https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/visual-studio-code-extension">Scan for secrets in Visual Studio Code</a></p></td><td></td><td></td></tr><tr><td><h3>Visual Studio</h3><p>Use the Snyk extension to scan for secrets in Visual Studio.</p><p><a href="https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/visual-studio-extension">Scan for secrets in Visual Studio</a></p></td><td></td><td></td></tr><tr><td><h3>JetBrains IDEs</h3></td><td>Use the Snyk plugin to scan for secrets in JetBrains IDEs.</td><td><a href="https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/jetbrains-plugin">Scan for secrets in JetBrains IDEs</a></td></tr><tr><td><h3>Eclipse</h3></td><td>Use the Snyk plugin to scan for secrets in the Eclipse IDE</td><td><a href="https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions/eclipse-plugin">Scan for secrets in Eclipse</a></td></tr></tbody></table>


---

# 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/scan-fix-and-prevent/scan-with-snyk/snyk-secrets/secrets-scanning-in-the-ide.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.
