Install LATdx, point it at your org, and get your first cached Apex test run in a few minutes.
This quickstart takes you from an empty PATH to a green Apex test run whose result replays instantly the next time.
Before you begin
You’ll need:
- An
sfdx-project.jsonworkspace (a standard Salesforce DX project). - An authenticated
sfCLI with at least one org you can run tests against. - Java 11+ on
PATH.
Install the LATdx CLI
The CLI ships as platform-specific release binaries.
macOS
curl -fsSL https://latdx.com/install.sh | bashVerify the binary is on your PATH:
latdx --helpFor version pinning, channels (stable / latest), and the in-place upgrade flow, see Installation & Upgrade. Windows ARM64 binaries are not published in v1.
Sign in to LATdx
Run latdx auth login to sign in. It opens your browser; approve the request and you’re done.
latdx auth loginIf your plan changes after you sign in (you join or leave a team, or start or cancel a subscription), LATdx checks it when access matters. Run latdx auth status any time to resolve your current plan from the site; latdx test run does the same before deciding whether the free-tier cap applies. If the site is unreachable, the last successful signed access proof is trusted for 24 hours, then runs drop to Free. The banner shows only local sign-in identity for new tokens, not live plan.
Sign-in is optional for a first run: unlicensed, latdx test run is capped at 100 tests per invocation. You can sign in even without a subscription: you get an identity token, and the resolver returns Free with the same 100-test cap until you subscribe. On a headless box or in CI, pass --no-browser to print the URL instead of opening one, or set LATDX_LICENSE_KEY directly. In CI (the CI env var set), unlimited runs require a TEAM/CI plan; Pro, Free, and unlicensed runs still work but stay at the same 100-test cap.
Run your first test
Run this from your project root, the directory that holds sfdx-project.json:
latdx test run -o my-orgThe first run executes every test and caches each result. Re-run it and the unchanged tests replay from cache in milliseconds.
Next: connect your AI agent
With tests running, most people next wire up their AI coding agent to run them. Attach LATdx over the Model Context Protocol and the agent runs your Apex tests through the CLI, reading back structured results instead of waiting on sf apex run test. For Claude Code or Codex it is one command:
Claude Code:
claude mcp add latdx -- latdx mcp serveCodex:
codex mcp add latdx -- latdx mcp serveFor Cursor, desktop apps, and the full tool list, see Use LATdx with an AI agent.