Reset Tracking doesn't work anymore with VS Code Extensions

[FabienTaillon]

Summary

Reset Tracking doesn't work anymore with VS Code Extensions, only with the CLI commands.

Steps To Reproduce:

1. Create a Scratch Org
2. Make changes in the org
3. Reset the tracking with the CLI, sf project reset tracking --no-prompt or via the Command Palette (SFDX: Reset Remote Tracking
4. Using the CLI preview, no change is detected (sf project retrieve preview or sf project retrieve start ), however when using the VS Code Extensions (SFDX: View All Changes (Local and in Default Org) or even SFDX: Pull Source from Default Org) all the changes are still there, listed and retrieved.

Expected result

No change is supposed to be listed.

Actual result

All changes are available via the VS Code Extensions (but not via the CLI), even though the reset command has been used.

Additional information

Salesforce Extension Version in VS Code: 66.8.0

Salesforce CLI Version: 2.131.7

OS and version: macOS 26.4.1

VS Code version: 1.117.0

Most recent version of the extensions where this was working: 🤷‍♂️

[svc-idee-bot]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[mshanemc]

on it

[mshanemc]

can you run the new SFDX: Generate Project Info and post the contents?

"Works on my machine problem" so there's probably strange with the extensions/settings.

side topic: what's making you need to reset tracking?

[FabienTaillon]

I noticed something: if I reload VS Code via the Command Palette (Developer: Reload Window), it works (changes are not listed anymore).

Also, If I pull the changes with the Command Palette, changes disappear from tracking as expected, but if I pull with the CLI changes are still listed (and I can pull them a second time with the Command Palette).
I'm not the only one in the team having this issue though and we have different setup (Windows vs Mac).

I reset mainly for 2 reasons:

• we create a scratch org, push metadata from local project, and after that sometimes some stuff appear in the org as changed and needing to be pulled even though we did nothing
• some changes are listed in source tracking and we don't want them. I have tracked the pull issues I've found here, and for instance this one will track changes in Permission Set we haven't touched (including standard ones with sweet names like sfdcInternalInt__sfdc_scrt2). Dirty option would be to delete the line from SourceMember, but it's usually easier to retrieve manually what we want and then reset tracking to get rid of the unwanted and tracked metadata. Other option is to pull everything and delete locally what we don't want in our project, but then on push it will try to delete them (another reason to reset to make the state clean).

Here is the project information:

# Project Info

Generated: 2026-04-28T13:37:12.617Z

## Metadata

sourceApiVersion: 66.0
packageDirectories: 1
namespace: 

### Types

| Type | Components | Files | Size (KB) |
| --- | --- | --- | --- |
| CustomObject | 1 | 3 | 1 |

## Org

| Key | Value |
| --- | --- |
| Org type | scratch |
| Source tracking | true |
| SourceMember count | 2 |

## Settings

| Setting | Value |
| --- | --- |
| salesforcedx-vscode-metadata.showSuccessNotification | false |
| salesforcedx-vscode-metadata.sourceTracking.pollingIntervalSeconds | 60 |
| salesforcedx-vscode-core.push-or-deploy-on-save.enabled | false |
| salesforcedx-vscode-core.push-or-deploy-on-save.ignoreConflictsOnPush | false |
| salesforcedx-vscode-core.detectConflictsForDeployAndRetrieve | false |
| salesforcedx-vscode-core.clearOutputTab | false |
| salesforcedx-vscode-core.show-cli-success-msg | true |
| salesforcedx-vscode-core.telemetry.enabled | true |
| salesforcedx-vscode-core.enable-sobject-refresh-on-startup | false |
| salesforcedx-vscode-core.telemetry-tag |  |
| salesforcedx-vscode-salesforcedx.enableLocalTraces | false |
| salesforcedx-vscode-salesforcedx.enableConsoleTraces | false |
| salesforcedx-vscode-salesforcedx.enableFileTraces | false |
| salesforcedx-vscode-apex.java.home | /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home |

## Environment

| Key | Value |
| --- | --- |
| Salesforce CLI | @salesforce/cli/2.131.7 darwin-arm64 node-v22.22.2 |
| Java | java 17.0.6 2023-01-17 LTS |
| VS Code | 1.117.0 |
| Node | v22.22.1 |
| OS | Darwin 25.4.0 |

## Extensions (Salesforce)

| Extension | Version |
| --- | --- |
| salesforce.apex-language-server-extension | 0.4.0 |
| salesforce.salesforcedx-einstein-gpt | 3.34.0 |
| salesforce.salesforcedx-metadata-visualizer-vscode | 1.0.2 |
| salesforce.salesforcedx-vscode-apex | 66.8.0 |
| salesforce.salesforcedx-vscode-apex-debugger | 66.8.0 |
| salesforce.salesforcedx-vscode-apex-log | 66.8.0 |
| salesforce.salesforcedx-vscode-apex-oas | 66.8.0 |
| salesforce.salesforcedx-vscode-apex-replay-debugger | 66.8.0 |
| salesforce.salesforcedx-vscode-apex-testing | 66.8.0 |
| salesforce.salesforcedx-vscode-core | 66.8.0 |
| salesforce.salesforcedx-vscode-expanded | 66.8.0 |
| salesforce.salesforcedx-vscode-lightning | 66.8.0 |
| salesforce.salesforcedx-vscode-lwc | 66.8.0 |
| salesforce.salesforcedx-vscode-metadata | 66.8.0 |
| salesforce.salesforcedx-vscode-org | 66.8.0 |
| salesforce.salesforcedx-vscode-org-browser | 66.8.0 |
| salesforce.salesforcedx-vscode-services | 66.8.0 |
| salesforce.salesforcedx-vscode-soql | 66.8.0 |
| salesforce.salesforcedx-vscode-ui-preview | 1.2.3 |
| salesforce.salesforcedx-vscode-visualforce | 66.8.0 |
| salesforce.sfdx-code-analyzer-vscode | 1.18.0 |