Choose a Glade workflow

Task guides

Start with the job in front of you. Each path names the interface, project setup, expected local result, and Salesforce boundary.

Daily code loop

Check Apex sourceGet a named local diagnostic or a clean result.
Start: glade check --project .
Interface: CLI or VS Code · Requires: projectRun Apex testsRun all, focused, changed, or failed tests locally.
Start: glade test --project .
Interface: CLI or VS Code · Requires: projectDebug ApexUse breakpoints or profile a saved log or local trace.
Start: glade dap --project .
Interface: CLI or VS Code · Requires: projectExecute Apex and SOQLRun anonymous Apex and queries against the local runtime.
Start: glade exec --project . "System.debug('local');"
Interface: CLI, VS Code, or local Playground · Requires: project

Local state

Work with local dataCreate a named SQLite-backed environment, seed records, and use supported local API routes.
Start: glade org create refinement-local
Interface: CLI or VS Code · Requires: project and local data

UI preview

Preview LWCOpen local component and page routes in the Workbench Console.
Start: glade dev lwc --project . --open
Interface: browser · Requires: project and toolchainPreview VisualforceServe supported pages and controller flows locally.
Start: glade dev vf --project .
Interface: browser · Requires: project

Team automation

Add Glade to CIPublish JSON, SARIF, JUnit, and stable exit-code evidence.
Start: glade check --project . --json
Interface: CI · Requires: project and pinned binary

Use How Glade works for subsystem boundaries, the CLI reference for exact flags, and What runs locally before relying on a hosted Salesforce edge.