> 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/fix/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/snyk-ide.md).

# Consistent Ignores for Snyk Code IDE

How Consistent Ignores for Snyk Code work in the IDE

When you run tests in any of the [supported Snyk IDE plugins](https://docs.snyk.io/developer-tools/integrations/snyk-ide-plugins-and-extensions), the plugins will take into account your ignores.

## Minimum version required

Snyk Code Consistent Ignores works best with the latest IDE plugin versions.

| IDE           | Minimum version required |
| ------------- | ------------------------ |
| VS Code       | 2.22.0                   |
| IntelliJ      | 2.13.1                   |
| Visual Studio | 2.2.1                    |
| Eclipse       | v20250516.122216         |

## Setup

To take ignores into account, specify the Organization where the ignores reside. [Group-level policies also cascade down to all Organizations](/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code.md#manage-ignores-at-the-group-level-through-snyk-code-security-policies). See [How to select the Organization to use in IDE plugins (Visual Studio Code example)](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli).

## Snyk IDE default ignore behavior

The IDE display output hides ignored results by default to maintain developer focus.

## View ignores in Snyk IDE

You can apply filters in the plugin settings to show ignored results alongside open results or in isolation. When you set ignored issues to display, the issues and their details appear in the plugin.


---

# 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/fix/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/snyk-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.