Repository: DataDog/documentation
Pull request #28826: [DOCS-10227] VS Code extension revamp
Author: login: joepeeples
Labels: name: Architecture
description: Everything related to the Doc backend
name: editorial review
description: Waiting on a more in-depth review
name: Images
description: Images are added/removed with this PR
name: mergequeue-status: done
Created: 2025-04-16T22:19:30Z | Merged: 2025-05-13T21:07:00Z

### What does this PR do? What is the motivation?
<!-- A brief description of the change being made with this pull request. What is your motivation for the PR? -->

Reorganizes and revises the product docs for Datadog's VS Code extension. Also brings attention to compatibility with Cursor and other forks & flavors.

### Merge instructions

<!-- 
If you're waiting for a release or there are other considerations that you want us to be aware of, list them here. 
If the PR is ready to be merged once it receives the required reviews, check the box below after you've created the PR.
-->

Merge readiness:
- [x] Ready for merge

**For Datadog employees**:
Merge queue is enabled in this repo. Your branch name MUST follow the `<name>/<description>` convention and include the forward slash (`/`). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

To have your PR automatically merged after it receives the required reviews, add the following PR comment:

```
/merge
```

### Additional notes
<!-- Anything else we should know when reviewing?-->

<!-- Previewing the PR: Assuming you are a Datadog employee and named your branch `<yourname>/<description>`, a preview build will run and links to the preview output will be auto-generated and posted in the PR comments. The links will 404 until the preview build is finished running. -->



Diff:
diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml
index f883aed35bf..313422a5a0a 100644
--- a/config/_default/menus/main.en.yaml
+++ b/config/_default/menus/main.en.yaml
@@ -1074,7 +1074,7 @@ menu:
       parent: ide_plugins_idea
       identifier: ide_plugins_idea_debugger
       weight: 7011
-    - name: VS Code
+    - name: VS Code & Cursor
       url: developers/ide_plugins/vscode/
       parent: ide_plugins
       identifier: ide_plugins_vscode
diff --git a/content/en/developers/ide_plugins/_index.md b/content/en/developers/ide_plugins/_index.md
index 04b1a40519e..546adf9f4cb 100644
--- a/content/en/developers/ide_plugins/_index.md
+++ b/content/en/developers/ide_plugins/_index.md
@@ -12,6 +12,6 @@ Use Datadog plugins in your preferred integrated development environment (IDE) t
 
 {{< whatsnext desc="See the documentation for information about the following integrations:">}}
     {{< nextlink href="developers/ide_plugins/idea/" >}}<u>JetBrains IDEs</u>: The Datadog plugin for IntelliJ IDEA, GoLand, PyCharm, WebStorm, and PhpStorm.{{< /nextlink >}}
-    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code.{{< /nextlink >}}
+    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code, Cursor, and other related forks.{{< /nextlink >}}
     {{< nextlink href="developers/ide_plugins/visual_studio/" >}}<u>Visual Studio</u>: The Datadog extension for .NET developers.{{< /nextlink >}}
 {{< /whatsnext >}}
\ No newline at end of file
diff --git a/content/en/developers/ide_plugins/vscode/_index.md b/content/en/developers/ide_plugins/vscode/_index.md
index 8d290b79384..77c68728f17 100644
--- a/content/en/developers/ide_plugins/vscode/_index.md
+++ b/content/en/developers/ide_plugins/vscode/_index.md
@@ -1,6 +1,6 @@
 ---
-title: Datadog Extension for Visual Studio Code
-description: Learn how to run Synthetic tests on local environments directly in VS Code.
+title: Datadog Extension for VS Code & Cursor
+description: Integrate Datadog telemetry and insights into your source code in VS Code and other IDEs.
 is_beta: true
 aliases:
 - '/developers/ide_integrations/vscode/'
@@ -19,6 +19,8 @@ further_reading:
   text: "Simplify production debugging with Datadog Exception Replay"
 ---
 
+<!-- TO CONTRIBUTORS: This content also exists in the extension's README file. Remember to update the README when you change anything in this file. -->
+
 {{% site-region region="gov" %}}
 <div class="alert alert-warning">
     The Datadog extension for Visual Studio Code is not supported for your selected <a href="/getting_started/site">Datadog site</a> ({{< region-param key="dd_site_name" >}}).
@@ -27,126 +29,121 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog's monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds annotations above your code to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+<div class="alert alert-info">This feature is only available for VS Code and Cursor. Other forks of VS Code are not supported.</div>
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-## Code Delta
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+## Static Code Analysis
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-## Static Analysis
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+### Get started with Static Code Analysis
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-### Getting started
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, search for the command `Datadog: Configure Static Analysis Languages` in the command palette (`Shift` + `Cmd` + `P` in macOS; `Ctrl` + `Shift` + `P` in Windows).
 
-{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="A banner for onboarding." style="width:100%;" >}}
+You can also run a batch analysis for individual folders and even the entire workspace. In the IDE's file explorer view, right-click a folder and select **Datadog Static Analysis > Analyze Folder** or **Analyze Workspace**.
 
-Once the configuration file is created, the static analyzer runs automatically in the background.
+<!-- <div style="width:600px; height:400px; background-color:#CCCCCC; display:flex; justify-content:center; align-items:center;">image placeholder: video of batch analysis</div><br /> -->
 
-<div class="alert alert-info">The Static Analysis feature does not require a Datadog account, as source files are analyzed locally.</div>
+<div class="alert alert-info">Static Code Analysis does not require a Datadog account, as source files are analyzed locally.</div>
 
 ## Exception Replay
 
-Exception Replay allows you to navigate through the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
+**Exception Replay** allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
 
-In order to get access to this feature, you have to enable [Error Tracking Exception Replay][29] on Datadog.
+To access this feature, you must enable [Error Tracking Exception Replay][11] on Datadog.
 
-After the feature has been enabled, you can see an `Exception Replay` button next to the stack trace section of any instrumented Error Tracking code insight. If you click over it, you can:
+After the feature has been enabled, you can see an **Exception Replay** button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
 
-- access all the information Datadog has about the different frames
-- navigate through the production code
-- review the value of the different variables involved
+- Access all the information Datadog has about the different frames.
+- Navigate through the production code.
+- Review the value of the different variables involved.
 
-Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. VS Code shows a new activity with two new views:
+Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
 
-- **Variables**: It shows the variables related to a particular stack trace frame.
-- **Stack Trace**: It allows you to navigate through the different stack trace frames.
+- **Variables**: Displays the variables related to a particular stack trace frame.
+- **Stack Trace**: Lists the stack frames for navigation.
 
 Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
 
@@ -154,45 +151,42 @@ Select a stack trace frame and inspect the values of all the variables that Data
 
 ## License
 
-Please read this [End-User License Agreement][23] carefully before downloading or using the Datadog Visual Studio Code Extension.
+Read the [End-User License Agreement][12] carefully before downloading or using the Datadog Visual Studio Code extension.
 
 ## Data and telemetry
 
-Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][24] and Datadog's [VS Code extension EULA][23].
+Datadog collects certain information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, what caused those errors, and user identifiers in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12]. This data is used to help improve the extension's performance and features, including transitions to and from the extension and the applicable Datadog login page for accessing the Services.
 
-If you don't wish to send this data to [Datadog][1], you can opt out at any time in the VS Code extension settings: `Datadog > Telemetry > Setup > Enable Telemetry` and select `disabled`.
+If you don't wish to send this data to [Datadog][3], you can disable this at any time in the extension's settings: `Datadog > Telemetry > Setup > Enable Telemetry` and select `disabled`.
 
 <div class="alert alert-info">The Datadog extension also honors the <a href="https://code.visualstudio.com/docs/configure/telemetry#_output-channel-for-telemetry-events">VS Code telemetry</a> setting.</div>
 
 ## Help and feedback
 
-To share your feedback, email [team-ide-integration@datadoghq.com][3] or create an issue in the extension's [public repository][26].
+To share your feedback, email [team-ide-integration@datadoghq.com][14] or create an issue in the extension's [public repository][15].
+
+Check out the [issues][16] section to discover known issues.
 
-Check out the [issues][27] section to discover known issues.
+Do you use [Cursor][17], or another fork of VS Code? Find the extension on the [Open VSX Registry][2].
 
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: https://www.datadoghq.com/
-[2]: https://marketplace.visualstudio.com/items?itemName=Datadog.datadog-vscode
-[3]: mailto:team-ide-integration@datadoghq.com
-[10]: /tracing/error_tracking/
-[11]: /security/code_security/software_composition_analysis/
-[12]: /continuous_integration/guides/flaky_test_management/
-[14]: /continuous_integration/static_analysis/?tab=githubactions
-[15]: /continuous_integration/static_analysis/rules/
-[16]: /logs/log_collection/javascript/
-[17]: https://github.com/winstonjs/winston
-[18]: https://github.com/pinojs/pino
-[19]: https://github.com/trentm/node-bunyan
-[20]: https://github.com/log4js-node/log4js-node
-[21]: https://docs.python.org/3/library/logging.html
-[22]: /continuous_integration/static_analysis/?tab=circleciorbs#setup
-[23]: https://www.datadoghq.com/legal/eula/
-[24]: https://www.datadoghq.com/legal/privacy/
-[25]: https://code.visualstudio.com/docs/getstarted/telemetry#_output-channel-for-telemetry-events
-[26]: https://github.com/DataDog/datadog-for-vscode
-[27]: https://github.com/DataDog/datadog-for-vscode/issues?q=is%3Aissue+label%3A%22known+issue%22
-[28]: /logs/explorer/
-[29]: /tracing/error_tracking/exception_replay
+[1]: https://marketplace.visualstudio.com/items?itemName=Datadog.datadog-vscode
+[2]: https://open-vsx.org/extension/datadog/datadog-vscode
+[3]: https://www.datadoghq.com/
+[4]: /logs/explorer/
+[5]: /tracing/error_tracking/
+[6]: /security/code_security/
+[7]: /tests/explorer/
+[8]: /continuous_integration/static_analysis/?tab=githubactions
+[9]: /security/code_security/static_analysis/static_analysis_rules/
+[10]: /security/code_security/static_analysis/setup/
+[11]: /tracing/error_tracking/exception_replay
+[12]: https://www.datadoghq.com/legal/eula/
+[13]: https://www.datadoghq.com/legal/privacy/
+[14]: mailto:team-ide-integration@datadoghq.com
+[15]: https://github.com/DataDog/datadog-for-vscode
+[16]: https://github.com/DataDog/datadog-for-vscode/issues?q=is%3Aissue+label%3A%22known+issue%22
+[17]: https://www.cursor.com/
diff --git a/static/images/developers/ide_plugins/vscode/code-insights-2.png b/static/images/developers/ide_plugins/vscode/code-insights-2.png
new file mode 100644
index 00000000000..bb220bc5fb3
Binary files /dev/null and b/static/images/developers/ide_plugins/vscode/code-insights-2.png differ
diff --git a/static/images/developers/ide_plugins/vscode/code-insights-inline-hover.mp4 b/static/images/developers/ide_plugins/vscode/code-insights-inline-hover.mp4
new file mode 100644
index 00000000000..6a94178774f
Binary files /dev/null and b/static/images/developers/ide_plugins/vscode/code-insights-inline-hover.mp4 differ
diff --git a/static/images/developers/ide_plugins/vscode/datadog-vscode-3.png b/static/images/developers/ide_plugins/vscode/datadog-vscode-3.png
new file mode 100644
index 00000000000..1a252f69e8a
Binary files /dev/null and b/static/images/developers/ide_plugins/vscode/datadog-vscode-3.png differ
diff --git a/static/images/developers/ide_plugins/vscode/file_insights_view.mp4 b/static/images/developers/ide_plugins/vscode/file_insights_view.mp4
new file mode 100644
index 00000000000..a14e4a6c0f6
Binary files /dev/null and b/static/images/developers/ide_plugins/vscode/file_insights_view.mp4 differ
diff --git a/static/images/developers/ide_plugins/vscode/view-in-vscode-2.png b/static/images/developers/ide_plugins/vscode/view-in-vscode-2.png
new file mode 100644
index 00000000000..c1e6cfa1e4c
Binary files /dev/null and b/static/images/developers/ide_plugins/vscode/view-in-vscode-2.png differ
diff --git a/static/images/developers/ide_plugins/vscode/view-in-vscode-error.png b/static/images/developers/ide_plugins/vscode/view-in-vscode-error.png
new file mode 100644
index 00000000000..39c7bc605ca
Binary files /dev/null and b/static/images/developers/ide_plugins/vscode/view-in-vscode-error.png differ


Reviews:
user: login: Vomain
body: Thanks a lot for the work @joepeeples! Left some comments here. 
FYI some screenshots are outdated or would benefit from better consistency (e.g. same background color and theme), I'll create new ones. I think we should move forward without them though. 
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-22T09:45:15Z
user: login: jfree
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-22T12:04:13Z
user: login: Vomain
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-23T18:44:42Z
user: login: Vomain
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-24T08:58:43Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-24T18:05:57Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-24T18:07:52Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-24T18:08:39Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-24T18:10:06Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-24T18:14:18Z
user: login: Vomain
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T13:54:07Z
user: login: Vomain
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T13:55:33Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T14:27:06Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T16:09:55Z
user: login: hestonhoffman
body: LGTM! I left one small suggestion. I'm to go ahead and approve despite that suggestion.
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T17:47:22Z
user: login: joepeeples
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-13T20:20:17Z

Review comments:
diff_hunk: @@ -12,6 +12,6 @@ Use Datadog plugins in your preferred integrated development environment (IDE) t
 
 {{< whatsnext desc="See the documentation for information about the following integrations:">}}
     {{< nextlink href="developers/ide_plugins/idea/" >}}<u>JetBrains IDEs</u>: The Datadog plugin for IntelliJ IDEA, GoLand, PyCharm, WebStorm, and PhpStorm.{{< /nextlink >}}
-    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code.{{< /nextlink >}}
+    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code, Cursor, and other related forks.{{< /nextlink >}}
path: content/en/developers/ide_plugins/_index.md
user: login: Vomain
body: If my memory is correct, I thought we were going for "flavors" instead of "forks". Did you change your mind?
created_at: 2025-04-22T09:35:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,6 +1,6 @@
 ---
-title: Datadog Extension for Visual Studio Code
-description: Learn how to run Synthetic tests on local environments directly in VS Code.
+title: Datadog Extension for VS Code, Cursor, and Related Forks
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: Vomain
body: I guess we can remove the word "Datadog" if it's too overloaded as is? Also maybe "Related" is not useful here?

> Extension for VS Code, Cursor and Other Forks
created_at: 2025-04-22T09:38:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: Vomain
body: "CodeLens" is not something devs really know about, it's a VS Code branded term. 
I'd replace:
> The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog.

with 
> The extension adds annotations above your code to detected logging patterns that match log records in Datadog.
created_at: 2025-04-22T09:39:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: Vomain
body: This feature only works for VS Code and Cursor, it doesn't work for other forks (since we need to manually add the entry in the menu for every new IDE, which means new icons and more importantly takes up valuable real estate in an already crammed menu). I'd mention it as a callout (alert-info).
created_at: 2025-04-22T09:41:59Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-## Code Delta
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+## Static Code Analysis
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-## Static Analysis
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+### Get started with Static Code Analysis
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-### Getting started
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+You can also run a batch analysis for individual folders and even the entire workspace. In the IDE's file explorer view, right-click a folder and select **Datadog Static Analysis > Analyze Folder** or **Analyze Workspace**.
 
-{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="A banner for onboarding." style="width:100%;" >}}
+<!-- <div style="width:600px; height:400px; background-color:#CCCCCC; display:flex; justify-content:center; align-items:center;">image placeholder: video of batch analysis</div><br /> -->
 
-Once the configuration file is created, the static analyzer runs automatically in the background.
-
-<div class="alert alert-info">The Static Analysis feature does not require a Datadog account, as source files are analyzed locally.</div>
+<div class="alert alert-info">Static Code Analysis does not require a Datadog account, as source files are analyzed locally.</div>
 
 ## Exception Replay
 
-Exception Replay allows you to navigate through the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
+**Exception Replay** allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
 
-In order to get access to this feature, you have to enable [Error Tracking Exception Replay][29] on Datadog.
+To access this feature, you must enable [Error Tracking Exception Replay][11] on Datadog.
 
-After the feature has been enabled, you can see an `Exception Replay` button next to the stack trace section of any instrumented Error Tracking code insight. If you click over it, you can:
+After the feature has been enabled, you can see an **Exception Replay** button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
 
-- access all the information Datadog has about the different frames
-- navigate through the production code
-- review the value of the different variables involved
+- Access all the information Datadog has about the different frames.
+- Navigate through the production code.
+- Review the value of the different variables involved.
 
-Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. VS Code shows a new activity with two new views:
+Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
 
-- **Variables**: It shows the variables related to a particular stack trace frame.
-- **Stack Trace**: It allows you to navigate through the different stack trace frames.
+- **Variables**: Displays the variables related to a particular stack trace frame.
+- **Stack Trace**: Lists the stack frames for navigation.
 
 Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
 
 {{< img src="/developers/ide_plugins/vscode/exception_replay.mp4" alt="Preview of Exception Replay" style="width:100%" video=true >}}
 
 ## License
 
-Please read this [End-User License Agreement][23] carefully before downloading or using the Datadog Visual Studio Code Extension.
+Read the [End-User License Agreement][12] carefully before downloading or using the Datadog Visual Studio Code extension.
 
 ## Data and telemetry
 
-Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][24] and Datadog's [VS Code extension EULA][23].
+Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12].
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: Vomain
body: After talking with legal, the actual wording should be:

> Datadog collects certain information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, what caused those errors, and [List the identifiers that are being collected] in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12]. This data is used to help improve the extension’s performance and features, including transitions to and from the extension and the applicable Datadog login page for accessing the Services.
created_at: 2025-04-22T09:42:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,6 +1,6 @@
 ---
-title: Datadog Extension for Visual Studio Code
-description: Learn how to run Synthetic tests on local environments directly in VS Code.
+title: Datadog Extension for VS Code, Cursor, and Related Forks
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: jfree
body: To add another view-point, I would go with `Datadog Extension for VS Code & Cursor`.  Those are the only two flavors we are officially backing at the moment, and by providing the Open VSX Registry info, we already open the door to others who want to experiment unofficially with other flavors (Windsurf etc).
created_at: 2025-04-22T12:04:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-## Code Delta
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+## Static Code Analysis
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-## Static Analysis
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+### Get started with Static Code Analysis
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-### Getting started
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+You can also run a batch analysis for individual folders and even the entire workspace. In the IDE's file explorer view, right-click a folder and select **Datadog Static Analysis > Analyze Folder** or **Analyze Workspace**.
 
-{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="A banner for onboarding." style="width:100%;" >}}
+<!-- <div style="width:600px; height:400px; background-color:#CCCCCC; display:flex; justify-content:center; align-items:center;">image placeholder: video of batch analysis</div><br /> -->
 
-Once the configuration file is created, the static analyzer runs automatically in the background.
-
-<div class="alert alert-info">The Static Analysis feature does not require a Datadog account, as source files are analyzed locally.</div>
+<div class="alert alert-info">Static Code Analysis does not require a Datadog account, as source files are analyzed locally.</div>
 
 ## Exception Replay
 
-Exception Replay allows you to navigate through the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
+**Exception Replay** allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
 
-In order to get access to this feature, you have to enable [Error Tracking Exception Replay][29] on Datadog.
+To access this feature, you must enable [Error Tracking Exception Replay][11] on Datadog.
 
-After the feature has been enabled, you can see an `Exception Replay` button next to the stack trace section of any instrumented Error Tracking code insight. If you click over it, you can:
+After the feature has been enabled, you can see an **Exception Replay** button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
 
-- access all the information Datadog has about the different frames
-- navigate through the production code
-- review the value of the different variables involved
+- Access all the information Datadog has about the different frames.
+- Navigate through the production code.
+- Review the value of the different variables involved.
 
-Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. VS Code shows a new activity with two new views:
+Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
 
-- **Variables**: It shows the variables related to a particular stack trace frame.
-- **Stack Trace**: It allows you to navigate through the different stack trace frames.
+- **Variables**: Displays the variables related to a particular stack trace frame.
+- **Stack Trace**: Lists the stack frames for navigation.
 
 Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
 
 {{< img src="/developers/ide_plugins/vscode/exception_replay.mp4" alt="Preview of Exception Replay" style="width:100%" video=true >}}
 
 ## License
 
-Please read this [End-User License Agreement][23] carefully before downloading or using the Datadog Visual Studio Code Extension.
+Read the [End-User License Agreement][12] carefully before downloading or using the Datadog Visual Studio Code extension.
 
 ## Data and telemetry
 
-Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][24] and Datadog's [VS Code extension EULA][23].
+Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12].
 
-If you don't wish to send this data to [Datadog][1], you can opt out at any time in the VS Code extension settings: `Datadog > Telemetry > Setup > Enable Telemetry` and select `disabled`.
+If you don't wish to send this data to [Datadog][3], you can opt out at any time in the extension's settings: `Datadog > Telemetry > Setup > Enable Telemetry` and select `disabled`.
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: Vomain
body: > If you don't wish to send this data to [Datadog][3], you can disable this at any time...
created_at: 2025-04-23T18:44:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,6 +1,6 @@
 ---
-title: Datadog Extension for Visual Studio Code
-description: Learn how to run Synthetic tests on local environments directly in VS Code.
+title: Datadog Extension for VS Code, Cursor, and Related Forks
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: Vomain
body: You're right for now, I guess we wanted to be somehow be future proof but that might be overthinking it 👍
```suggestion
title: Datadog Extension for VS Code & Cursor
```
created_at: 2025-04-24T08:58:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: joepeeples
body: ```suggestion
Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds annotations above your code to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
```
created_at: 2025-04-24T18:05:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-## Code Delta
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+## Static Code Analysis
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-## Static Analysis
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+### Get started with Static Code Analysis
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-### Getting started
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+You can also run a batch analysis for individual folders and even the entire workspace. In the IDE's file explorer view, right-click a folder and select **Datadog Static Analysis > Analyze Folder** or **Analyze Workspace**.
 
-{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="A banner for onboarding." style="width:100%;" >}}
+<!-- <div style="width:600px; height:400px; background-color:#CCCCCC; display:flex; justify-content:center; align-items:center;">image placeholder: video of batch analysis</div><br /> -->
 
-Once the configuration file is created, the static analyzer runs automatically in the background.
-
-<div class="alert alert-info">The Static Analysis feature does not require a Datadog account, as source files are analyzed locally.</div>
+<div class="alert alert-info">Static Code Analysis does not require a Datadog account, as source files are analyzed locally.</div>
 
 ## Exception Replay
 
-Exception Replay allows you to navigate through the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
+**Exception Replay** allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
 
-In order to get access to this feature, you have to enable [Error Tracking Exception Replay][29] on Datadog.
+To access this feature, you must enable [Error Tracking Exception Replay][11] on Datadog.
 
-After the feature has been enabled, you can see an `Exception Replay` button next to the stack trace section of any instrumented Error Tracking code insight. If you click over it, you can:
+After the feature has been enabled, you can see an **Exception Replay** button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
 
-- access all the information Datadog has about the different frames
-- navigate through the production code
-- review the value of the different variables involved
+- Access all the information Datadog has about the different frames.
+- Navigate through the production code.
+- Review the value of the different variables involved.
 
-Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. VS Code shows a new activity with two new views:
+Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
 
-- **Variables**: It shows the variables related to a particular stack trace frame.
-- **Stack Trace**: It allows you to navigate through the different stack trace frames.
+- **Variables**: Displays the variables related to a particular stack trace frame.
+- **Stack Trace**: Lists the stack frames for navigation.
 
 Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
 
 {{< img src="/developers/ide_plugins/vscode/exception_replay.mp4" alt="Preview of Exception Replay" style="width:100%" video=true >}}
 
 ## License
 
-Please read this [End-User License Agreement][23] carefully before downloading or using the Datadog Visual Studio Code Extension.
+Read the [End-User License Agreement][12] carefully before downloading or using the Datadog Visual Studio Code extension.
 
 ## Data and telemetry
 
-Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][24] and Datadog's [VS Code extension EULA][23].
+Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12].
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: joepeeples
body: @Vomain looks like this still has a placeholder `[List the identifiers that are being collected]` — what should we put in its place?
created_at: 2025-04-24T18:07:51Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-## Code Delta
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+## Static Code Analysis
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-## Static Analysis
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+### Get started with Static Code Analysis
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-### Getting started
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+You can also run a batch analysis for individual folders and even the entire workspace. In the IDE's file explorer view, right-click a folder and select **Datadog Static Analysis > Analyze Folder** or **Analyze Workspace**.
 
-{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="A banner for onboarding." style="width:100%;" >}}
+<!-- <div style="width:600px; height:400px; background-color:#CCCCCC; display:flex; justify-content:center; align-items:center;">image placeholder: video of batch analysis</div><br /> -->
 
-Once the configuration file is created, the static analyzer runs automatically in the background.
-
-<div class="alert alert-info">The Static Analysis feature does not require a Datadog account, as source files are analyzed locally.</div>
+<div class="alert alert-info">Static Code Analysis does not require a Datadog account, as source files are analyzed locally.</div>
 
 ## Exception Replay
 
-Exception Replay allows you to navigate through the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
+**Exception Replay** allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
 
-In order to get access to this feature, you have to enable [Error Tracking Exception Replay][29] on Datadog.
+To access this feature, you must enable [Error Tracking Exception Replay][11] on Datadog.
 
-After the feature has been enabled, you can see an `Exception Replay` button next to the stack trace section of any instrumented Error Tracking code insight. If you click over it, you can:
+After the feature has been enabled, you can see an **Exception Replay** button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
 
-- access all the information Datadog has about the different frames
-- navigate through the production code
-- review the value of the different variables involved
+- Access all the information Datadog has about the different frames.
+- Navigate through the production code.
+- Review the value of the different variables involved.
 
-Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. VS Code shows a new activity with two new views:
+Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
 
-- **Variables**: It shows the variables related to a particular stack trace frame.
-- **Stack Trace**: It allows you to navigate through the different stack trace frames.
+- **Variables**: Displays the variables related to a particular stack trace frame.
+- **Stack Trace**: Lists the stack frames for navigation.
 
 Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
 
 {{< img src="/developers/ide_plugins/vscode/exception_replay.mp4" alt="Preview of Exception Replay" style="width:100%" video=true >}}
 
 ## License
 
-Please read this [End-User License Agreement][23] carefully before downloading or using the Datadog Visual Studio Code Extension.
+Read the [End-User License Agreement][12] carefully before downloading or using the Datadog Visual Studio Code extension.
 
 ## Data and telemetry
 
-Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][24] and Datadog's [VS Code extension EULA][23].
+Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12].
 
-If you don't wish to send this data to [Datadog][1], you can opt out at any time in the VS Code extension settings: `Datadog > Telemetry > Setup > Enable Telemetry` and select `disabled`.
+If you don't wish to send this data to [Datadog][3], you can opt out at any time in the extension's settings: `Datadog > Telemetry > Setup > Enable Telemetry` and select `disabled`.
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: joepeeples
body: ```suggestion
If you don't wish to send this data to [Datadog][3], you can disable this at any time in the extension's settings: `Datadog > Telemetry > Setup > Enable Telemetry` and select `disabled`.
```
created_at: 2025-04-24T18:08:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: joepeeples
body: Added info alert in 39fad84a8da8453080f657801f7e35d2d4580bfa
created_at: 2025-04-24T18:10:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -12,6 +12,6 @@ Use Datadog plugins in your preferred integrated development environment (IDE) t
 
 {{< whatsnext desc="See the documentation for information about the following integrations:">}}
     {{< nextlink href="developers/ide_plugins/idea/" >}}<u>JetBrains IDEs</u>: The Datadog plugin for IntelliJ IDEA, GoLand, PyCharm, WebStorm, and PhpStorm.{{< /nextlink >}}
-    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code.{{< /nextlink >}}
+    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code, Cursor, and other related forks.{{< /nextlink >}}
path: content/en/developers/ide_plugins/_index.md
user: login: joepeeples
body: Haha, my memory was actually "forks" because it sounds a bit more technical and officially separate from VS Code & Microsoft, but I think our discussion is lost to Slack. Either one works, just let me know what you think resonates with dev audiences and I can make sure it's consistent throughout.
created_at: 2025-04-24T18:14:18Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-## Code Delta
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+## Static Code Analysis
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-## Static Analysis
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+### Get started with Static Code Analysis
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-### Getting started
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+You can also run a batch analysis for individual folders and even the entire workspace. In the IDE's file explorer view, right-click a folder and select **Datadog Static Analysis > Analyze Folder** or **Analyze Workspace**.
 
-{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="A banner for onboarding." style="width:100%;" >}}
+<!-- <div style="width:600px; height:400px; background-color:#CCCCCC; display:flex; justify-content:center; align-items:center;">image placeholder: video of batch analysis</div><br /> -->
 
-Once the configuration file is created, the static analyzer runs automatically in the background.
-
-<div class="alert alert-info">The Static Analysis feature does not require a Datadog account, as source files are analyzed locally.</div>
+<div class="alert alert-info">Static Code Analysis does not require a Datadog account, as source files are analyzed locally.</div>
 
 ## Exception Replay
 
-Exception Replay allows you to navigate through the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
+**Exception Replay** allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
 
-In order to get access to this feature, you have to enable [Error Tracking Exception Replay][29] on Datadog.
+To access this feature, you must enable [Error Tracking Exception Replay][11] on Datadog.
 
-After the feature has been enabled, you can see an `Exception Replay` button next to the stack trace section of any instrumented Error Tracking code insight. If you click over it, you can:
+After the feature has been enabled, you can see an **Exception Replay** button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
 
-- access all the information Datadog has about the different frames
-- navigate through the production code
-- review the value of the different variables involved
+- Access all the information Datadog has about the different frames.
+- Navigate through the production code.
+- Review the value of the different variables involved.
 
-Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. VS Code shows a new activity with two new views:
+Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
 
-- **Variables**: It shows the variables related to a particular stack trace frame.
-- **Stack Trace**: It allows you to navigate through the different stack trace frames.
+- **Variables**: Displays the variables related to a particular stack trace frame.
+- **Stack Trace**: Lists the stack frames for navigation.
 
 Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
 
 {{< img src="/developers/ide_plugins/vscode/exception_replay.mp4" alt="Preview of Exception Replay" style="width:100%" video=true >}}
 
 ## License
 
-Please read this [End-User License Agreement][23] carefully before downloading or using the Datadog Visual Studio Code Extension.
+Read the [End-User License Agreement][12] carefully before downloading or using the Datadog Visual Studio Code extension.
 
 ## Data and telemetry
 
-Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][24] and Datadog's [VS Code extension EULA][23].
+Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12].
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: Vomain
body: @joepeeples `user identifiers`
created_at: 2025-05-06T13:54:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -12,6 +12,6 @@ Use Datadog plugins in your preferred integrated development environment (IDE) t
 
 {{< whatsnext desc="See the documentation for information about the following integrations:">}}
     {{< nextlink href="developers/ide_plugins/idea/" >}}<u>JetBrains IDEs</u>: The Datadog plugin for IntelliJ IDEA, GoLand, PyCharm, WebStorm, and PhpStorm.{{< /nextlink >}}
-    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code.{{< /nextlink >}}
+    {{< nextlink href="developers/ide_plugins/vscode/" >}}<u>Visual Studio Code</u>: The Datadog extension for VS Code, Cursor, and other related forks.{{< /nextlink >}}
path: content/en/developers/ide_plugins/_index.md
user: login: Vomain
body: @joepeeples you're right, `fork` seems like the commonly used term now
created_at: 2025-05-06T13:55:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,162 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds CodeLens annotations to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-## Code Delta
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+## Static Code Analysis
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-## Static Analysis
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+### Get started with Static Code Analysis
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-### Getting started
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+You can also run a batch analysis for individual folders and even the entire workspace. In the IDE's file explorer view, right-click a folder and select **Datadog Static Analysis > Analyze Folder** or **Analyze Workspace**.
 
-{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="A banner for onboarding." style="width:100%;" >}}
+<!-- <div style="width:600px; height:400px; background-color:#CCCCCC; display:flex; justify-content:center; align-items:center;">image placeholder: video of batch analysis</div><br /> -->
 
-Once the configuration file is created, the static analyzer runs automatically in the background.
-
-<div class="alert alert-info">The Static Analysis feature does not require a Datadog account, as source files are analyzed locally.</div>
+<div class="alert alert-info">Static Code Analysis does not require a Datadog account, as source files are analyzed locally.</div>
 
 ## Exception Replay
 
-Exception Replay allows you to navigate through the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
+**Exception Replay** allows you to inspect the stack trace frames of any Error Tracking code insight and get information about the values of the variables of the code running in production.
 
-In order to get access to this feature, you have to enable [Error Tracking Exception Replay][29] on Datadog.
+To access this feature, you must enable [Error Tracking Exception Replay][11] on Datadog.
 
-After the feature has been enabled, you can see an `Exception Replay` button next to the stack trace section of any instrumented Error Tracking code insight. If you click over it, you can:
+After the feature has been enabled, you can see an **Exception Replay** button next to the stack trace section of any instrumented Error Tracking code insight. Click the button to:
 
-- access all the information Datadog has about the different frames
-- navigate through the production code
-- review the value of the different variables involved
+- Access all the information Datadog has about the different frames.
+- Navigate through the production code.
+- Review the value of the different variables involved.
 
-Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. VS Code shows a new activity with two new views:
+Select an Error Tracking code insight from the Code Insights view. Go to the stack trace and click the Exception Replay button. The IDE shows a new activity with two new views:
 
-- **Variables**: It shows the variables related to a particular stack trace frame.
-- **Stack Trace**: It allows you to navigate through the different stack trace frames.
+- **Variables**: Displays the variables related to a particular stack trace frame.
+- **Stack Trace**: Lists the stack frames for navigation.
 
 Select a stack trace frame and inspect the values of all the variables that Datadog captured from your production code.
 
 {{< img src="/developers/ide_plugins/vscode/exception_replay.mp4" alt="Preview of Exception Replay" style="width:100%" video=true >}}
 
 ## License
 
-Please read this [End-User License Agreement][23] carefully before downloading or using the Datadog Visual Studio Code Extension.
+Read the [End-User License Agreement][12] carefully before downloading or using the Datadog Visual Studio Code extension.
 
 ## Data and telemetry
 
-Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][24] and Datadog's [VS Code extension EULA][23].
+Datadog anonymously collects information about your usage of this IDE, including how you interact with it, whether errors occurred while using it, and what caused those errors, in accordance with the [Datadog Privacy Policy][13] and Datadog's [VS Code extension EULA][12].
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: joepeeples
body: Revised in 73e6dc5616e59bcaf8dda602ed7501251ff27fb5
created_at: 2025-05-06T14:27:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,164 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog’s monitoring and security tools and sign up for a free trial.  
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: joepeeples
body: ```suggestion
  - New to Datadog? [Learn more][3] about Datadog's monitoring and security tools and sign up for a free trial.  
```
created_at: 2025-05-13T16:09:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,164 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog's monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds annotations above your code to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+<div class="alert alert-info">This feature is only available for VS Code and Cursor. Other forks of VS Code are not supported.</div>
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-## Code Delta
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+## Static Code Analysis
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-## Static Analysis
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+### Get started with Static Code Analysis
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-### Getting started
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: hestonhoffman
body: Might help to have the Windows equivalent shortcut too. (Ctrl + Shift + P.)
created_at: 2025-05-13T17:45:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -27,172 +29,164 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development.
+The Datadog extension for Visual Studio Code (VS Code) integrates with Datadog to accelerate your development. It is also available for Cursor and other forks of VS Code. To install in your preferred integrated development environment (IDE):
 
-{{< img src="/developers/ide_plugins/vscode/datadog-vscode-2.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
+- [Visual Studio Marketplace][1]: Install the extension for VS Code.
+- [Open VSX Registry][2]: Download the VSIX file to install for Cursor and other forks of VS Code.
 
-It packs several features, including:
+{{< img src="/developers/ide_plugins/vscode/datadog-vscode-3.png" alt="The Datadog for VS Code extension" style="width:100%;" >}}
 
-- [**Code Insights**](#code-insights) to keep you informed about
+The extension includes these features:
 
-  - Issues from [Error Tracking][10]
-  - Reports by [Application Vulnerability Management][11]
-  - [Flaky tests][12] detected by CI Visibility
+- [**Log Annotations**](#log-annotations): Gauge log volumes and search logs from your code.
 
-- [**View in VS Code**](#view-in-vs-code) to directly go from your file references on the Datadog platform to your source files.
+- [**Code Insights**](#code-insights): Stay informed about runtime errors, vulnerabilities, and flaky tests without leaving the code.
 
-- [**Logs Navigation**](#logs-navigation) to allow you to search for logs from your code.
+- [**View in IDE**](#view-in-ide): Jump directly from code references in Datadog to your source files.
 
-- [**Code Delta**](#code-delta) to more accurately map observability data to your files in VS Code.
+- [**Static Code Analysis**](#static-code-analysis): Detect and fix problems before you commit changes.
 
-- [**Static Analysis**](#static-analysis) to detect and fix problems even before you commit changes.
+- [**Exception Replay**](#exception-replay): Debug your production code.
 
-- [**Exception Replay**](#exception-replay) to help you debug your production code.
+<div class="alert alert-info">Unless stated otherwise, all extension features are available for both VS Code and any other IDEs based on VS Code forks, such as Cursor.</div>
 
 ## Requirements
 
-- **A Datadog account**: The extension requires a Datadog account (except when using [Static Analysis][14] features). If you're new to Datadog, go to the [Datadog website][1] to learn more about Datadog's observability tools and sign up for a free trial.
+- **Datadog account**: Most features require a Datadog account.  
+  - New to Datadog? [Learn more][3] about Datadog's monitoring and security tools and sign up for a free trial.  
+  - If your organization uses a custom sub-domain such as `myorg.datadoghq.com`, you must indicate it using the `datadog.connection.oauth.setup.domain` setting.
 
-- **VS Code Git**: The extension works better when VS Code Git integration is enabled. You can ensure that the integration is enabled by checking the `git.enabled` setting.
+- **Git**: The extension works better when Git is enabled in the IDE. Ensure this is enabled by checking the `git.enabled` setting.
 
-## Setup
+## Log annotations
 
-Install the [Datadog Extension][2] from the Visual Studio Marketplace.
+Use **Log Annotations** to gauge the volume of logs generated by a given log line in your code. The extension adds annotations above your code to detected logging patterns that match log records in Datadog. Click an annotation to open the [Log Explorer][4] in Datadog and view the matching logs.
 
-## Code Insights
+{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
 
-The **Code Insights** tree displays insights generated by the Datadog platform that are relevant to your code-base. The insights are grouped into three categories: performance, reliability, and security.
+You can also search Datadog logs from within VS Code. Select any text in the code editor, then right-click and select **Datadog \> Search Logs With Selected Text**.
 
-{{< img src="/developers/ide_plugins/vscode/code-insights.png" alt="The Code Insights view." style="width:100%;" >}}
+{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
 
-Code Insights include a detailed description for each issue, and links to:
+## Code insights
 
-- The related source code location
-- The Datadog platform for additional information
+**Code insights** keep you informed with Datadog-generated insights that are relevant to your code base:
 
-You can dismiss individual Code Insights and set filters to view the ones you are most interested in.
+- Runtime errors collected by [Error Tracking][5]  
+- Code and library vulnerabilities reported by [Code Security][6]  
+- Flaky tests detected by [Test Optimization][7]
 
-## View in VS Code
+The extension identifies errors and vulnerabilities in the code with colored squiggles; hover over the line for more details.
 
-The **View in VS Code** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][10]):
+{{< img src="/developers/ide_plugins/vscode/code-insights-inline-hover.mp4" alt="Hovering over inline code insights" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/view-in-vscode.png" alt="A stack trace on the Datadog platform showing the View in VS Code button." style="width:100%;" >}}
+The **Code Insights** view in the Datadog sidebar lists all the issues found in the repository. Select an item to view the full insight, and use the links to jump to the related source code location or open the code insight in Datadog.
 
-<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
+You can group code insights by kind, file, priority, or service. You can also ignore individual code insights and set filters to view the ones you're most interested in.
 
-## Logs navigation
+{{< img src="/developers/ide_plugins/vscode/code-insights-2.png" alt="The Code Insights view." style="width:100%;" >}}
 
-You can navigate to the [Log Explorer][28] on the [Datadog platform][1] directly from your source code files.
+For specific insights about the file currently open in the active editor, check the **File Insights** view in the IDE's file explorer. This view also lists issues discovered by [Static Code Analysis](#static-code-analysis) within the file.
 
-If you're using a supported logging library, the extension is able to show you code lenses on the lines where it has detected log patterns that match the Datadog platform records:
+{{< img src="/developers/ide_plugins/vscode/file_insights_view.mp4" alt="File Insights view" style="width:100%" video=true >}}
 
-{{< img src="/developers/ide_plugins/vscode/logs_navigation.mp4" alt="Preview of Logs Navigation" style="width:100%" video=true >}}
+## View in IDE
 
-The supported logging libraries are:
+<div class="alert alert-info">This feature is only available for VS Code and Cursor. Other forks of VS Code are not supported.</div>
 
-- JavaScript
-  - [@datadog/browser-logs][16]
-  - [Winston][17]
-  - [Pino][18]
-  - [Bunyan][19]
-  - [Log4js][20]
-- Python
-  - [logging][21]
+The **View in VS Code** or **View in Cursor** feature provides a link from Datadog directly to your source files. Look for the button next to frames in stack traces displayed in the UI (for example, in [Error Tracking][5]):
 
-Alternatively, you can select some text in your source code, right click on them, and look for the **Datadog > Search Logs With Selected Text** option.
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-2.png" alt="A stack trace in Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-{{< img src="developers/ide_plugins/vscode/log_search.png" alt="Using the Datadog Log explorer feature" style="width:100%;" >}}
+You can also use this feature to open your source files from an insight (such as an error from Error Tracking):
 
-## Code Delta
+{{< img src="/developers/ide_plugins/vscode/view-in-vscode-error.png" alt="An Error Tracking issue in the Datadog showing the View in VS Code button" style="width:100%;" >}}
 
-Code Delta matches the line numbers included in Datadog telemetry to the line numbers of the files you are currently working on in VS Code.
+<div class="alert alert-info">To use this feature, first configure <a href="/integrations/guide/source-code-integration/">source code integration</a> for your service.</div>
 
-For example, all [View in VS Code](#view-in-vs-code) links on the Datadog platform encode runtime version info, and the extension uses that to compute the corresponding line of code in your editor, taking into account version changes.
+## Static Code Analysis
 
-You can tweak the Code Delta settings to change how the matching algorithm works. In particular, you can modify the `Minimum Affinity` value, which determines the degree of confidence required to match lines.
+[Static Code Analysis][8] analyzes your code (locally) against predefined rules to detect and fix problems.
 
-## Static Analysis
+The extension runs Static Code Analysis rules on the source files you have open in your workspace. This allows you to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in the code before you commit your changes.
 
-The [Static Analysis][14] integration analyzes your code (locally) against predefined rules to detect and fix problems.
+Static Code Analysis supports scanning for many programming languages. For a complete list, see [Static Code Analysis Rules][9]. For file types belonging to supported languages, issues are shown in the source code editor, and you can directly apply suggested fixes.
 
-The Datadog extension runs [Static Analysis][14] rules on the source files you have open in your Workspace. The goal is to detect and fix problems such as maintainability issues, bugs, or security vulnerabilities in your code before you commit your changes.
+{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
 
-[Static Analysis][14] supports scanning for many programming languages. For a complete list, see [Static Analysis Rules][15]. For file types belonging to supported languages, issues are shown in the source code editor with the VS Code inspection system, and suggested fixes can be applied directly.
+### Get started with Static Code Analysis
 
-{{< img src="/developers/ide_plugins/vscode/static_analysis.mp4" alt="Preview of Static Analysis" style="width:100%" video=true >}}
+When you start editing a source file, the extension checks for [`static-analysis.datadog.yml`][10] at your source repository's root. It prompts you to create it if necessary.
 
-### Getting started
+{{< img src="/developers/ide_plugins/vscode/static-analysis-onboard.png" alt="Onboarding banner for setting up Static Code Analysis with Python files" style="width:75%;" >}}
 
-When you start editing a source file, the extension checks for [static-analysis.datadog.yml][22] at your source repository's root. It prompts you to create it if necessary.
+After you create the configuration file, the analyzer runs automatically in the background whenever you open a file. If you need to enable Static Code Analysis for a particular language, use the `Datadog: Configure Static Analysis Languages` command from the command palette (`Shift` + `Cmd` + `P`, then search for the command).
path: content/en/developers/ide_plugins/vscode/_index.md
user: login: joepeeples
body: Added in 8f8ead49ec77974d01cb0a66a2865d98cbe0397d
created_at: 2025-05-13T20:20:17Z
author_association: CONTRIBUTOR

PR comments:
user: login: github-actions[bot]
created_at: 2025-04-16T22:22:45Z
body: ## Preview links (active after the `build_preview` check completes)




### Modified Files
* https://docs-staging.datadoghq.com/joepeeples/10227-vscode-revamp/developers/ide_plugins/
* https://docs-staging.datadoghq.com/joepeeples/10227-vscode-revamp/developers/ide_plugins/vscode/
author_association: CONTRIBUTOR
user: login: maycmlee
created_at: 2025-05-06T15:25:21Z
body: Created docs card for review: https://datadoghq.atlassian.net/browse/DOCS-10801
author_association: CONTRIBUTOR
user: login: datadog-datadog-prod-us1[bot]
created_at: 2025-05-12T22:03:19Z
body: # Datadog Summary

<b>✅&nbsp;Code Quality</b>&nbsp;&nbsp;&nbsp;&nbsp;<b>✅&nbsp;Code Security</b>&nbsp;&nbsp;&nbsp;&nbsp;<b>✅&nbsp;Dependencies</b>



---
Was this helpful? Give us [feedback](https://dd.enterprise.slack.com/archives/C01FA7FASUR)!

author_association: CONTRIBUTOR
user: login: joepeeples
created_at: 2025-05-13T20:20:39Z
body: /merge
author_association: CONTRIBUTOR
user: login: dd-devflow[bot]
created_at: 2025-05-13T20:20:43Z
body: <!-- "FeedbackWorkflowId":"f971b156-7981-44d2-8389-d3d6156a9bab_36" -->
[View all feedbacks in Devflow UI.](https://mosaic.us1.ddbuild.io/devflow/logs/f971b156-7981-44d2-8389-d3d6156a9bab_36)

`2025-05-13 20:20:43 UTC` :information_source: Start processing command `/merge`

---
`2025-05-13 20:20:49 UTC` :information_source: **MergeQueue:** waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
**Note:** if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with `/remove` command.

---
`2025-05-13 20:50:15 UTC` :information_source: **MergeQueue:** merge request added to the queue

The expected merge time in `master` is approximately 20m (p90).

---
`2025-05-13 21:07:05 UTC` :information_source: **MergeQueue:** This merge request was merged

author_association: NONE