Give your agent a feedback loop.
Let your coding agent check its work with local tests and concrete diagnostics—not guesswork.
Build an AI-assisted workflowA little more local. A lot less waiting.
Run Apex locally. Keep your momentum.
Check source, run supported Apex tests, and debug in your Salesforce DX project—on your own machine, before a deploy.
Supported local workflows, not a replacement for Salesforce. Check the boundaries.
Explore an illustrated workflow Try the workflow
AccountServiceTest.clsAPEX
@IsTest
private class AccountServiceTest {
@IsTest static void createsAccount() {
Account acc = new Account(Name = 'Acme');
insert acc;
Assert.areEqual('Acme', acc.Name);
}
}
Test results
$glade test --project . --class AccountServiceTest
AccountServiceTest.createsAccountPassed
1 test executed · 1 passed · 0 failed
Scripted website preview · simulated output. No Apex runs here. Run a real example locally.
Test one change
Run a focused, supported Apex test before deploying your project.
Inspect the result
Debug supported Apex locally and inspect the variables that explain a failure.
Keep your workspace
Work from your Salesforce DX project in your editor or terminal.
Use the same local loop in automation
Add scoped local checks to your workflow. Keep Salesforce validation as a separate gate.
Less context switching
Stay in the code.
Not the deploy queue.
A local feedback loop that fits the way you already work. No new project format. No org login for supported local checks.
01
Start with your project.
Open your Salesforce DX workspace.
02
Make a change. See the result.
Check, test, and debug supported Apex locally.
03
Validate when you’re ready.
Keep Salesforce as your final validation gate.
acme-salesforce — Visual Studio Code
AccountService.cls
public class AccountService {
public static Account create() {
Account acc = new Account(
Name = 'Acme');
insert acc;
return acc;
}
}
Paused at breakpoint · line 5
acc.Name "Acme"
main Glade · local debug
acme-salesforce — terminal
$glade doctor --project .
✓ Project found. Ready.
$glade check --project .
✓ No source diagnostics.
$glade test --project .
--class AccountServiceTest
✓ createsAccount · 1 test passed
main Local project
An agent workflow using the Glade CLI
“Add a regression test. Prove it fails, fix the source, and rerun with Glade.”
Write a focused failing test
AccountServiceTest.createsAccount
Use the local result to make the fix
glade test --project . --class ... --json
Rerun and report the evidence
Named test · diagnostic · exit status
Bring your own agentGlade provides the local feedback
Illustrative workflow previews · initialized Salesforce DX project. Read the guides
A small tool. Room to grow.
Make the workflow yours.
Start with the local runtime. Connect it to the tools and workflows that help you build.
Take local checks into CI.
Run checks and affected tests on pull requests. Keep machine-readable reports with your build.
Add Glade to your pipelineAdd only what you need.
Extend Glade with optional first-party plugins for advisory project scans and org-backed package artifact capture.
Explore pluginsBuilt on clear boundaries
Local first.
Not a Salesforce replacement.
Glade gives you earlier feedback on supported paths. Some APIs use limited or deterministic local models. Validate hosted services and production behavior in Salesforce.
See what runs locallyWorkflowWhere it runs
Apex checks & supported testsInside your Salesforce DX project
LocalSupported SOQL & DMLAgainst local data
LocalHosted services & final validationAgainst the real platform
SalesforceGo from waiting to making.
Start with one local test.
Install Glade on macOS or Linux, then choose the small sample or your own Salesforce DX project.
curl -fsSL https://glade.sh/install.sh | sh