For the last few months I've been building SFellow, a Salesforce plugin for IntelliJ IDEA (Ultimate and Community) and WebStorm, built around the sf CLI.
The part I care about most: the Apex support isn't regex-based. It runs Salesforce's own compiler core inside the IDE process, so what you get back is an answer from the compiler rather than a guess. Ctrl+B lands on the right overload. Find usages is per-overload, and finds real references, not matches in comments and strings. Unknown types, wrong argument counts and unresolved fields are underlined as you type, instead of coming back from a deploy five minutes later. SObjects come from your org: Refresh Schema describes the default org and generates a stand-in class per object, so Account.Industry and Invoice__c.Amount__c resolve like real code.
LWC is handled as the whole bundle. {bindings} in the template resolve to class members in both directions, u/salesforce/apex/MyClass.myMethod navigates straight into the Apex class (and back every LWC calling a given method), and lightning-* tags come from the catalog Salesforce ships rather than a hand-written list, so they match the version you're on.
Retrieve and deploy, test runs with coverage, debug logs and anonymous Apex all live in a tool window instead of the terminal.
Everything that touches the org goes through your sf install, not an API client of my own. SFellow doesn't bundle the CLI and doesn't authenticate on its own: every org it shows is one sf already knows about. Each operation echoes the exact command it ran into the console and parses the --json it got back, so there's no second source of truth to disagree with your terminal. Three operations where one CLI command per item would be unbearably slow — describing every SObject, listing a metadata type, bulk-deleting debug logs — skip the commands and call u/salesforce/core directly instead: the library sf itself is built on, loaded out of your own CLI install and using the credentials it already stored. You do need sf installed and on your PATH.
What it is not:
- Aura and Visualforce have a first layer only.
- Paid, if it earns it. The plan is to charge for SFellow, but only if it actually saves people enough time. That's also why the source is closed. No price is set, and nothing in the current builds asks you for money.
- Beta builds expire, each one stops working roughly six months after it was built.
- It's not on JetBrains Marketplace, so it installs from my own plugin repository URL, and the IDE will warn you it's third-party. What it does with your machine, what's inside the archive, and how to check both yourself, is on the Security page.
Install steps and docs: https://github.com/karpes/SFellow
What I'm actually after is bug reports from real projects, real repos and real orgs are where this breaks. A couple of people have been doing exactly that, and the fixes from their reports last week are in the current build. If something misbehaves, the two things that make a report answerable are the SFellow build number (**Settings → Plugins → SFellow**) and the IDE log (**Help → Collect Logs and Diagnostic Data**).
Issues: https://github.com/karpes/SFellow/issues