Web Dashboard

sfdt ui starts a local Express server and opens the SFDT dashboard in your browser. It reads log/result files from your project’s logDir (default logs/) and can run several commands live.

sfdt ui                   # opens http://localhost:7654
sfdt ui --port 8080       # custom port
sfdt ui --no-open         # start without opening the browser

Pages

All 27 pages, in nav order — the page list is generated from the dashboard’s own route registry, so it cannot drift from the app:

Data appears automatically after running the corresponding CLI commands (sfdt test, sfdt preflight, sfdt drift, …) that write JSON result files.

SOQL Console

The SOQL Console page (deep-linkable at /soql) puts the whole sfdt soql family on the dashboard. Its /api/soql/* routes are thin wrappers over the CLI’s own soql-runner.js — the single query/schema engine shared with the CLI, MCP, and VS Code — so results, bounds, and error messages are identical across surfaces.

• Schema browser — search sObjects (all / custom / standard), then browse a describe: field types, active picklist values, reference targets, and a Relationships tab with parent lookups (dot notation) and child relationships (subqueries). Query this seeds the editor with a starter query.
• Validate — local static checks plus an org LIMIT 0 round-trip that never materialises rows. An unreachable org degrades to a local-only verdict with a warning — never a fabricated org pass.
• Plan — the org’s query plans via the REST explain endpoint; the query is never executed.
• Run — bounded execution, never unbounded: the row cap comes from the limit field or soql.defaultLimit (default 200), clamped to soql.maxLimit (default 2000). The result shows the applied bound (appended / kept / clamped) and a truncation warning when the org holds more rows. FIND {…} queries route to SOSL automatically. Tooling API and deleted/archived-rows toggles match the CLI flags.
• Export — download the raw records as JSON, or as CSV rendered by the runner’s own CSV shaping (nested parent fields flatten to dot-path columns like Owner.Name) — the same output sfdt soql query --out writes.

Manifest Builder

The Manifest Builder page (Release group) is a changeset-style package.xml builder: browse metadata by type, tick checkboxes, watch a live XML preview, and save the result into your manifest directory (manifestDir, default manifest/release/).

• Two sources. The Org source lists an org’s real inventory (sf org list metadata-types / sf org list metadata), served from the latest Scan snapshot when it’s fresh — the Refresh from org button re-queries live. The Local source globs your local source tree instead. If the org can’t be listed you get a visible error with a Retry button — never a silently empty tree.
• Whole-type wildcard. Ticking Entire type (*) for a metadata type emits <members>*</members> instead of enumerating every member.
• Live preview, one renderer. The XML pane updates on every tick and is rendered server-side by the same engine every SFDT surface uses (renderPackageXml) — what you preview is byte-for-byte what gets saved.
• Selections persist per org in your browser (and separately for the Local source), with a one-click Clear all.
• Saving writes rl-<name>-package.xml; existing files are never overwritten (you get a conflict error instead), and the deployed/ archive folder is refused. Copy and download buttons are there for ad-hoc use.

Destructive mode

Switching the mode toggle to Destructive turns the selection into a deletion manifest, with a prominent warning. Saving writes a paired set:

When sfdt deploy picks up a release whose manifest has a -destructiveChanges.xml companion, the SFDT_DESTRUCTIVE_TIMING setting controls when the deletions run relative to the deploy: pre (delete before deploying), post (after — the default), none (skip deletions), or only (run only the destructive operation). The Release Hub deploy step exposes the same choice as radio buttons.

Live command runners

The Test Runs, Preflight, Drift, Compare, Pull, Audit, and Monitor pages have Run buttons that trigger the underlying command over a Server-Sent Events stream — output appears line-by-line in real time, exactly like running the CLI.

The Scratch (create / delete / pool-fill), Data (export / import / delete), and Docs (generate) pages add real mutating actions behind in-app confirmation dialogs — which also work inside the VS Code-embedded dashboard (no window.confirm).

AI chat drawer

The toolbar’s Ask AI button opens a sliding chat panel. Pages with relevant output (Review, Explain, Drift, Preflight) pre-fill the chat with that context so you can ask follow-ups without copy-pasting.

Security

• Binds to 127.0.0.1 — never exposed to the network.
• Per-launch auth token prevents unauthorized access to a running process.
• CSRF protection — all mutating routes require an X-SFDT-CSRF header.
• Read-only AI sandbox — the AI chat’s tool access is restricted to Read,Grep,Glob (no Bash/Write/Edit), so a prompt injection in page context can’t drive tool execution.
• Log redaction at ingest — secrets are redacted before reaching the in-memory buffer or the live SSE stream.

The same bridge endpoints the dashboard exposes are what the Chrome extension talks to — see The Bridge.