Agent
Add an agent panel when readers of a Snowflake native app dashboard should ask a Cortex agent questions in place.
The live chat runs against a Cortex agent in your own Snowflake account; static exports and renders like this one show this placeholder instead.
What you can do
agentis the fully qualified name of a Snowflake Cortex agent,database.schema.agent.- An agent panel carries no
datablock and accepts noonClick; the chat runs against a Cortex agent in your own Snowflake account. - Static exports and renders show a placeholder in the panel; the live chat needs an interactive session.
Applies to an agent panel wherever the deployment allowlists the agent you name. The dvt Snowflake native app allowlists exactly one — its own — and registers it at install, when that registration succeeds; on self-host an operator sets the allowlist once at deploy time, so the FQN there is theirs to choose. The hosted dvt Gallery sets no allowlist, so the panel asks you to connect a Snowflake identity and every turn is refused.
Spec
View spec
{
"id": "ask-finance",
"type": "agent",
"title": "Ask the finance agent",
"spec": {
"agent": "ANALYTICS.FINANCE.REVENUE_AGENT"
}
}The only field is the agent FQN; there is no query, because the agent, not the panel, decides what data it reads.
Build it in dvt
Every block on this page is a few lines of the same declarative JSON spec. Read the full spec format, or connect an AI agent to your warehouse and build one live in the quickstart.
Follow the build
dvt is in founding research. Leave your email and we'll reach out when there's something to see — no newsletters, no noise.