# Workspace settings that conflict with VSCode settings

**URL:** <https://forum.cursor.com/t/workspace-settings-that-conflict-with-vscode-settings/28499>\
**Category:** Feature Requests\
**Created:** [November 18, 2024, 2:48pm UTC](https://forum.cursor.com/t/workspace-settings-that-conflict-with-vscode-settings/28499 "2024-11-18T14:48:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pmolodo](https://avatars.discourse-cdn.com/v4/letter/p/2acd7d/32.png) [@pmolodo](https://forum.cursor.com/u/pmolodo)\
**Post date:** [July 16, 2025, 9:46pm UTC](https://forum.cursor.com/t/workspace-settings-that-conflict-with-vscode-settings/28499/2 "2025-07-16T21:46:04Z")

</div>

I made a feature request for this:

> [@Cursor-specific overrides to .vscode/settings.json](https://forum.cursor.com/t/cursor-specific-overrides-to-vscode-settings-json/118861):
>
> I often work with codebases that have committed .vscode/settings.json files, targeted towards people who are using vscode, and not cursor. However, there are some settings that may conflict between cursor or vscode - for instance, many of these projects have "python.languageServer": "Pylance", which cursor the forces to "python.languageServer": "None". It would be helpful to have a way to override .vscode/settings.json settings with cursor-specific ones. A few ways of implementing this might…

---

_[View the full topic](https://forum.cursor.com/t/workspace-settings-that-conflict-with-vscode-settings/28499)._