Task guides and troubleshooting
Complete a task
These guides start from a known state, show the action, and name the expected result.
Run the first local checkOutcome: a configured project and a checked source tree.
Interface: terminal · Time: about 5 minutes.Run one Apex testOutcome: focus a local test loop on one class or method.
Interface: terminal and VS Code · Time: about 3 minutes.Debug Apex with breakpointsOutcome: stop in a local Apex test and inspect state.
Interface: VS Code · Time: about 10 minutes.Use anonymous Apex scratchOutcome: execute a local snippet and inspect output.
Interface: VS Code · Time: about 5 minutes.Work with local dataOutcome: seed and query a local environment.
Interface: terminal · Time: about 10 minutes.Run changed tests before a PROutcome: select only tests affected by your changes.
Interface: terminal and CI · Time: about 5 minutes.Profile an Apex debug logOutcome: analyze saved debug-log events locally.
Interface: terminal · Time: about 5 minutes.Add Glade to CIOutcome: emit a reliable local check, test, and report gate.
Interface: CI · Time: about 15 minutes.
Interface: terminal · Time: about 5 minutes.Run one Apex testOutcome: focus a local test loop on one class or method.
Interface: terminal and VS Code · Time: about 3 minutes.Debug Apex with breakpointsOutcome: stop in a local Apex test and inspect state.
Interface: VS Code · Time: about 10 minutes.Use anonymous Apex scratchOutcome: execute a local snippet and inspect output.
Interface: VS Code · Time: about 5 minutes.Work with local dataOutcome: seed and query a local environment.
Interface: terminal · Time: about 10 minutes.Run changed tests before a PROutcome: select only tests affected by your changes.
Interface: terminal and CI · Time: about 5 minutes.Profile an Apex debug logOutcome: analyze saved debug-log events locally.
Interface: terminal · Time: about 5 minutes.Add Glade to CIOutcome: emit a reliable local check, test, and report gate.
Interface: CI · Time: about 15 minutes.
Fix a problem
Start from the symptom or exact setup failure. The troubleshooting page gives the shortest diagnostic path before linking back to a task guide.
Check support and trust
Report a bug or share workflow feedback. Include the command, version, OS, expected/actual result, and a minimal public reproduction. Do not upload proprietary source, private package names, credentials, or customer records. Report vulnerabilities through the private security route, not public issues.
Confirm what Glade runs locally and review the release and plugin trust boundaries.
What Glade runs locallySearch supported APIs, named limits, and paths that still require Salesforce.Security & trustVerify releases, checksums, SBOMs, attestations, and plugin execution boundaries.
Use the error reference when output includes a stable Glade error code.