Trino Query Control Center

[gowthamrajj]

Changes

• New Query Control Center (DJ: Query Control Center) — a master-detail panel that replaces the Query View for inspecting and triaging Trino queries. A Live tab (queries from your active coordinator, or the local Trino CLI when no profile is set, with a "dbt runs only" filter) and a History tab both support search, state, and user/source filtering. Selecting a query shows its summary, stage tree, slowest operators, failure details, and SQL, plus Jump to Model (opens the matching .model.json) and Analyze with AI, which saves sanitized JSON under .dj/diagnostics/ so analyzed queries reopen even after the coordinator evicts them (~15 min).
• Named Trino connection profiles. dj.trino.profiles and dj.trino.activeProfile define coordinator profiles (dev / staging / prod) you switch from the panel or DJ: Select Trino Connection Profile.... Each profile resolves its secret at request time from VS Code SecretStorage (set via DJ: Set Trino Credentials...), an environment variable, a password file, or your ~/.dbt/profiles.yml — never plain text in settings — and the panel shows a coordinator status indicator with one-click refresh for expired tokens.
• New dj-trino-analyzer agent skill (.agents/skills/dj-trino-analyzer/SKILL.md, written when dj.codingAgent is on) gives a coding agent operator-level heuristics for diagnosing slow or failed Trino queries from the sanitized JSON. The sanitizer doubles as a tool firewall: payloads containing row data are rejected before they reach disk, so customer data never reaches an LLM prompt.

[arunxdev]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.