CLI to web deep links
When the CLI and web UI run against the same project, you can jump from terminal output into the investigation UI without retyping queries.
Setup
- Start the web app and note its origin (for example
http://127.0.0.1:5173).
bash
npx @dbt-tools/web --dbt-target ./target- Export the base URL (no trailing path required):
bash
export DBT_TOOLS_WEB_BASE_URL=http://127.0.0.1:5173- Run CLI commands with
--json. When the base URL is set, JSON may includeweb_urlandreview_url; human output can append an “Open in web” line.
URL shapes
The CLI builds query-string URLs aligned with the web workspace:
| Command | Typical web_url params |
|---|---|
discover | view=inventory and q= (discover query; omitted for filter-only discovery) |
explain | view=inventory, resource=<unique_id>, assetTab=summary |
Example discover output (conceptual):
text
http://127.0.0.1:5173/?view=inventory&q=ordersExample explain output (conceptual):
text
http://127.0.0.1:5173/?view=inventory&resource=model.my_project.orders&assetTab=summaryDownstream impact in the web UI uses lineage tab semantics (assetTab=lineage) in helpers—pair CLI deps --direction downstream with the web lineage view when handoff links are enabled for impact-style flows.
Workflow
See Open the same context in the browser.
Learn more
- Discovery parity
- CLI README — discover section