A DQL step is a structured query (read-only SQL) over your collection’s data so you can quickly filter, group, and aggregate. You can run DQL over metadata, transcripts, and the output of prior Reading steps. Your coding agent generates DQL steps as part of Analysis Plans. Example use cases for DQL steps include:Documentation Index
Fetch the complete documentation index at: https://docs.transluce.org/llms.txt
Use this file to discover all available pages before exploring further.
Reading and revising DQL steps
In an analysis plan, DQL steps run by default. You can see the results as a table in the UI, and the DQL query that generated them above it. The results table does not sort or filter in place. To order rows, ask your coding agent to put the ordering in the query (e.g., “sort by suspiciousness” adds anORDER BY clause).
DQL steps have deeply linked IDs. When sorting or filtering, ask your coding agent to include an ID column (e.g., agent_runs.id) in the SELECT. Any ID column in the results table renders as a clickable link that opens the linked transcript inline, so you can read the run that produced each row without leaving the plan.

