Workbench

The modern replacement for Salesforce Workbench and Benchpress

Workbench is a Salesforce administration toolkit that embeds directly into your browser — bringing an overlay panel, a VS Code editor, a full metadata explorer, a SOQL editor, and an AI agent capable of controlling your browser, all from a single Chrome extension.

---

What You Get

	Always at hand Overlay embedded in your Salesforce pages A non-intrusive panel appears on every Salesforce page, giving you instant access to tools, logs, and org data without ever leaving your current context.
Code without context switching VS Code editor running in your local browser A full-featured code editor opens directly inside your browser, powered by the same engine as VS Code. Write, run, and debug Apex without switching windows.
	Full visibility into your org Full workbench to interact and explore metadata Browse every object, field, permission set, and metadata component. Run SOQL, compare records, push changes, and manage your org from one focused interface.
Query with confidence Modern SOQL editor built for Salesforce Browse every SObject, write SOQL with autocomplete, and see results instantly. A focused query interface designed to replace the old Workbench query tool.
	AI that actually does work Powerful AI agent capable of controlling your browser The AI agent doesn't just answer questions — it takes actions. Navigate Salesforce pages, fill forms, run queries, and complete multi-step org tasks autonomously.

---

More Screenshots

Org Management

Side Panel

Quick Record Edit

_{Desktop App (in development)}

---

Available Platforms

Platform	Status	Link
Web Extension	Recommended	Add to Chrome
Desktop (macOS / Windows)	In development	Coming soon

---

Repository Layout

packages/lwc/app              Main LWC application modules
packages/lwc/web-extension    LWC modules specific to extension surfaces
packages/server               Dev/prod backend server modules plus LWR assets/layouts/hooks/content
packages/extension            Chrome extension entry points and manifest template
packages/shared/modules       Shared cross-target modules (shared/*)
packages/workers/src          Worker source files
packages/vendor-bundles       Vendor build wrappers (OpenAI/just-bash)
tools/build                   Rollup configs
tools/scripts                 Utility scripts and generators
assets                        Shared repository assets (images, skills, data, docs/refactor notes)
apps/ui                       Landing page and welcome app (React + Vite)
dist                          Build outputs (dist/web, dist/extension)

---

Prerequisites

• Node.js 22.14 (matches package.json engines)
• npm

---

Setup

git clone https://github.com/grebmann1/workbench.git
cd workbench
npm install

Create a .env file in the project root:

CLIENT_SECRET='YOUR_CLIENT_SECRET'
CLIENT_ID='YOUR_CLIENT_ID'

Optional vars:

Variable	Default	Description
PORT	3000	Server port
REDIRECT_URI	—	OAuth redirect URI
DOC_VERSION	—	Documentation version
CHROME_ID	—	Chrome extension ID
PROXY_URL	—	Proxy URL

---

Common Commands

Web App

# Dev server
npm run start:dev:web

# Production build
npm run build:web

# Production server
npm run start:prod:server

# Build and run production
npm run start:prod:web

Desktop App

# Build the desktop package
npm run build:desktop

# Start the desktop app against an already-running local web server
npm run start:dev:desktop

# Start both the local web server and the desktop app together
npm run start:dev:desktop:all

# Open the desktop app through the launcher CLI
npm run desktop:open

Chrome Extension

# Dev (main + sandbox watch + local serve)
npm run start:dev:extension

# Production build (extension + workers)
npm run build:prod:extension

# Main-only build
npm run build:extension:main

Workers

npm run watch:workers
npm run build:workers

Quality / Validation

npm run lint
npm run check
npm run validate

---

Chrome Extension — Local Load

1. Build extension output (npm run build:dev:extension).
2. Open chrome://extensions/.
3. Enable Developer mode.
4. Click Load unpacked.
5. Select dist/extension.

The extension build outputs manifest.json in dist/extension (generated from manifest.template.json).

---

Architecture Notes

• lwr.config.json controls routes, module resolution, and static assets for the web app.
• Rollup configs under tools/build control extension and worker bundles.
• Vendor browser bundles are generated under packages/vendor-bundles and copied into packages/server/assets/libs.
• Agent default skill content is generated into packages/shared/modules/defaultAgentSkills.

HMR Notes

A known LWR issue can break hot reload by dropping the LWC namespace during recompilation. This project auto-applies a patch after install via npm run postinstall (tools/scripts/patch_lwr_hmr_namespace.mjs).

If hot reload behaves inconsistently, clear cache and restart the dev server:

rm -rf __lwr_cache__
npm run start:dev:web

---

Where To Add Code

Area	Location
New app-level pages / features	packages/lwc/app/pages and packages/lwc/app/application
Shared LWC UI shell elements	packages/lwc/app/component
Extension-only components	packages/lwc/web-extension
Cross-target reusable modules	packages/shared/modules
Server hooks / routes / content / layout	packages/server

---

Roadmap

• Continue improving code analyzer and metadata tooling
• Expand data/object assignment analysis
• Improve extension localhost and debugging workflows
• Incrementally improve shared module boundaries and package ergonomics
• Release Desktop app for macOS and Windows

---

Contribution

Contributions are welcome. Please open issues or pull requests for improvements, fixes, and new tooling modules.

---

Open Source Acknowledgments

• LWC SOQL Builder
• Salesforce Inspector Reloaded
• Apex Log Analyzer — blazing-fast Salesforce Apex debug log analyzer for VS Code, with flame charts, SOQL/DML analysis, and Apex insights

---

License

MIT