Run supported Apex locally. Keep your momentum.
Site · Quickstart · Support map · Security · Feedback
Glade is an open-source, clean-room local Apex runtime and developer toolkit. Run supported tests, inspect and debug code, and exercise local SOQL, DML, and triggers without deploying to an org. Keep Salesforce for final validation and hosted platform behavior.
Glade reads source and metadata from disk and executes supported behavior in its own runtime. The CLI, VS Code extension, and local browser tools are interfaces to that runtime—not a hidden Salesforce org.
Glade is an independent open-source project and is not affiliated with, sponsored by, or endorsed by Salesforce. Salesforce and Apex are trademarks of Salesforce, Inc.
curl -fsSL https://glade.sh/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"
glade versionContinue with the canonical quickstart and choose the path that matches your workspace:
- Small terminal sample: create a temporary Salesforce DX project and run the documented test.
- Your own project: initialize an existing Salesforce DX project and run one known test class before the full suite.
- Optional browser example: load Refinement Service in a fresh managed workspace, then run its named test locally.
The Quickstart uses commands available in the current stable CLI and also
covers recovery, API-version rules, and the Salesforce boundary. The bundled
RefinementServiceTest first shipped in v0.2.14 and is included in the
v0.2.15 stable release.
For an existing Salesforce DX project, substitute a test class that it owns:
test -f glade.yml || glade init --project . --yes
glade doctor --project .
glade check --project .
glade test --project . --class RefinementServiceTest --json --no-progressA first project test result must name at least one executed test. The
installation guide covers macOS/Linux
archives, pinning, and verification; source development has a
separate guide. Building Glade requires
the Go version in go.mod and a C compiler with CGO enabled. See
AGENTS.md and AI contributor setup for the
repository workflow and validation commands.
| Job | Local result | Next step |
|---|---|---|
| Develop and debug | Run one test, inspect a failure, set a breakpoint, fix and rerun | Tests and debugging |
| Work with data | Seed isolated local state and exercise SOQL, DML, and triggers | Local data |
| Automate feedback | Use the same CLI in an editor, advisory CI, or an AI-assisted workflow | CI, AI workflow |
LWC/Visualforce previews, local HTTP APIs, package contracts, and report tools are deeper workflows. Start with How Glade works or Choose a workflow.
- Supported local behavior is not blanket Salesforce parity. Hosted services, live auth, deployment, exact Lightning Experience behavior, and final production validation remain with Salesforce.
- Checked Apex source versions are 65.0, 66.0, and 67.0. Historical sources may be preserved without checked correctness credit; Execute Anonymous and LWC have stricter eligibility. Checked HTTP endpoints are a separate axis: 60.0, 65.0, 66.0, and 67.0.
- Local test isolation is not an OS sandbox. Plugins run as your user. Review network use by custom code and external AI providers.
- Preview and deterministic harness behavior have named limits. A supported harness row does not implement the corresponding live hosted service.
Use the support map, known gaps, stdlib ledger, compatibility policy, and Apex language contract for detail. Counts apply to their named catalogs, not all Salesforce behavior.
Glade Tools contains maintenance and
extension workflows. @glade/performance provides advisory scans;
@glade/orgpackage supports package contracts; @glade/compat is
maintainer-facing compatibility tooling. Product and plugin versions are
independent—verify the pairing your team uses.
See plugin installation and trust. Glade Tools source and first-party plugin archives are licensed under Apache-2.0 and carry project and bundled dependency notices. Base Glade does not depend on Tools internals.
Report a bug or tell us about your workflow. Include version, OS/architecture, command, expected/actual result, test count, and a minimal public reproduction. Do not share proprietary source, private package names, credentials, or customer records.
Use private vulnerability reporting for security issues. See SECURITY.md and CONTRIBUTING.md. The pilot guide helps teams evaluate one representative path before making it a merge gate.
Glade source, documentation, examples, site source, and the VS Code extension are licensed under the Apache License 2.0. Copyright 2026 Matt Simonis.