SF Org Scout

Working in the same Salesforce org as your team? SF Org Scout tells you who changed what, and warns you before you deploy over someone else's work.

What it does

Live change feed. A timeline in the sidebar showing recent changes to Apex classes, triggers, Lightning Web Components, Lightning pages (FlexiPages) and custom fields, with who made each change and when. New components are tagged so you can tell a fresh build from an update.

Notifications. A heads-up when a teammate deploys something, like "Sara just deployed LWC accountSummary (2 min ago)".

Overwrite warnings. If a teammate changes something you have in your local project after your last retrieve, it's flagged in yellow on the timeline and you get a warning before you deploy over it.

Compare with the org. Click any change to diff your local copy against the org version. Lightning Web Components expand to show only the files that differ.

Retrieve in one click. A Retrieve button in the compare view pulls the org version into your project, with a confirmation first so you can't overwrite your work by accident.

Search and filters. Search classes, triggers, LWCs, pages or fields to see when they last changed and by whom. Filter the feed by time window or person, or hide your own changes.

Requirements

• The Salesforce CLI (sf) installed and on your PATH.
• A Salesforce DX project (sfdx-project.json) open in VS Code.
• A default org set for the project (sf config set target-org <alias>).
• Each teammate logs in with their own Salesforce user, so the "who" information is meaningful.

Only you need the extension. It reads change information straight from the org, so it sees everyone's changes, including teammates without the extension and changes made in Setup or the Developer Console.

How it works

SF Org Scout uses your existing sf CLI login. Every few minutes (5 by default) it asks the org which components changed since the last check, which is a handful of small API calls. It reads metadata names, dates and users; it only fetches source code when you open a compare, and it only writes to your project when you confirm a Retrieve.

Nothing is sent anywhere except to your own Salesforce org.

Settings

Good to know

• The overwrite warning compares the org's last-modified time with your local files. Any save to a local file counts as being in sync, so editing a file after a teammate's deploy but before the next check can hide the warning.
• "All" in the time window means everything seen since SF Org Scout started tracking in that project, not the org's entire history.
• Managed package components are ignored.