Skip to main content

Query and Dwaar AI

Sooner or later you will have a question the filters did not anticipate. "Which public repositories have a critical secret finding?" should not need a data export and a spreadsheet.

Query​

note

The Query page is in preview. The GraphQL API underneath it is available now. See the GraphQL reference.

Query takes a question across your findings, resources and components, turns it into a read-only GraphQL query, and lets you edit it and run it yourself. You always see the query, so you can check what it actually asked. Reads cost query units, counted under Settings › Usage, and a costly query Dwaar builds waits for you to run it. The History tab keeps what you ran.

Ask a question with Query walks through the page. Build a query, with examples shows how to approach a question, with queries you can copy.

Suggest products and lineage​

Suggest with AI proposes how your resources connect and which products should exist, for you to approve one by one. It sits on the Lineage views and the Products list and not in the assistant, because its answer is a list of decisions and not a conversation. See Suggest products and lineage with AI.

The assistant​

The floating assistant answers questions about whatever you are looking at. It works on the findings list, a single finding, a resource, or your workspace as a whole.

What you ask forWhat it doesWhere it runs
SummarySummarizes what is in view.Findings list, resource, workspace
ExplainExplains one finding.A single finding
AskAnswers a free question, using the thread's last turns as history.All of the above

It respects the filters on the Findings page. Choose Include hidden checks to include what those filters leave out for one answer. Later questions use the page filters again.

Answers cite records, so you can click through and check the claim. Do that, particularly before you act on one.

Two tiers are available to members: Fast and Reasoning. Administrators control the rest in AI settings.

Try this next​

Open your worst finding and ask the assistant to explain it. Then ask the question you would really ask a colleague: what breaks if we fix this?