AI product readSalesforce developer productivity tool that injects a code search and developer utilities panel directly into Salesforce setup pages (Classic and Lightning)
Salesforce developers and admins lack a fast way to search across Apex classes, triggers, Visualforce pages, Lightning components, and other code components within the Salesforce setup interface. The native Salesforce setup UI requires navigating through multiple pages to find and access code components.
1. User navigates to Salesforce Setup home page (Classic or Lightning). 2. The extension injects a tabbed developer utilities panel into the setup page. 3. On first use, user clicks 'Authorize' to initiate Salesforce OAuth2 flow - selecting org type (Production/Sandbox/Developer). 4. User is redirected to Salesforce login, grants OAuth consent, and is redirected back via callback.html. 5. The Firebase backend exchanges the auth code for tokens (access_token, refresh_token). 6. Tokens are stored in localStorage for subsequent API calls. 7. User can now search code components (using Salesforce Tooling API), run static analysis, extract code coverage, edit LWC components, explore GraphQL, and look up record details - all without leaving the setup page.
Code search across Apex Classes, Apex Triggers, Visualforce Pages, Visualforce Components, and Lightning ComponentsAdvanced quick-find sidebar navigation to code components from setup pagesCode coverage extraction and analysisStatic code analysis using Lightning Linter serviceRecord details lookup by Record IDLWC (Lightning Web Component) Editor
- Target users
- Salesforce developers / Salesforce administrators / Salesforce technical consultants
- The build/static/js/main.9a2068da.js is a minified React bundle (482KB) that is difficult to fully analyze, though it appears to be related to a secondary LWC editor or GraphQL explorer feature
- Could not fully verify whether the Firebase Cloud Functions backend imposes any usage limits or has paid tiers
- The monaco-editor directory is very large (1000+ files) and contains third-party VS Code editor code, not extension-specific logic
MonetizationNo paid features detected
No evidence of paid features, premium tiers, subscriptions, or payment mechanisms within the extension. Searches for 'premium', 'pricing', 'stripe', 'payment', and 'billing' returned no relevant matches in the extension's own code. The 'subscription' matches are all from monaco-editor internals (event subscriptions, not billing). The 'upgrade' matches are about browser/IndexedDB upgrades. The 'checkout' match in contentScript_l.js is a Twitter sharing link ('Checkout the updated version...'). The 'license' matches are all standard open-source library license declarations (MIT, React, etc.). All features (code search, static analysis, code coverage, LWC editor, GraphQL explorer) appear to be freely available without any gating.
- Confidence
- 90
- Payment platform
- --
- Source
- AI / High
- Login required
- Yes
- Reason
- The extension requires Salesforce OAuth2 authorization to function. Users must authorize the extension to access their Salesforce org data via OAuth flow. login.html presents org type selection (Sandbox/Production/Developer), login.js initiates Salesforce OAuth2 with a Connected App client ID, callback.js exchanges the auth code via a Firebase backend (us-central1-sf-advanced-code-searcher.cloudfunctions.net/authorizeSalesforce), and factory.js stores tokens (accessToken, refreshToken, instanceURL). Multiple directives check authenticationStatus and block features when 'Auth Needed'. The contentScript_l.js shows 'Click here to authorize (one time)' button and a 'Re-Authenticate' link. This is a one-time Salesforce OAuth grant, not a recurring login to the extension's own account system.
HUGE shoutout to Alan Garcia (alnandr) for the temp fix - THAAANNNKKKK YOOOOUUUU - we are back in business
I've never written a review but didn't realize how much I needed this extension until it wasn't working. Shoutout to Alan Garcia (alnandr) for posting the fix, I can confirm it works.
This extension is still fully functional, the issue is that Salesforce changed the name of the setup header element in the Spring '25 release that caused the injection to break. To anyone reading this who wants to get the advanced code searcher to work again in the meantime until the developer pushes an update, follow these steps: 1. Uninstall the extension from Chrome either from the nav bar or from chrome://extensions 2. Use a "CRX Extractor/Downloader" tool extension to download this Chrome extension as a ZIP file. 3. Extract the ZIP file contents to a folder somewhere you'll keep it long-term (i.e., Documents folder). 4. Open the contentScript_l.js file in the root directory using a text editor or IDE like VS Code. 5. On lines 16 and 29, replace ".onesetupHelpBanner" with ".onesetupSetupHeader" and save the file. 6. Navigate to chrome://extensions in your browser and enable developer mode. 7. Select "Load unpacked" and choose the extracted root directory from step 2. 8. Load Salesforce Setup in Lightning again and voila, the extension works again! Hope this helps everyone :)
Broken since Winter 25'. Please fix. everyone email [email protected] to get it fixed.
After the new release the extension's UI disappeared. Please fix it urgently.
I gave it a 5 because I love this extension. It doesn't work for me any longer. Maybe Winter 2025 release caused the issue. Please fix.
Not working anymore
Was working very well. Not working now. Kindly check and fix
Was working very well. Not working now. Last saw it working on Feb 2025
Was working very well. Not working now. Last saw it working on Feb 28th