Human objective
Present, discover, compare, monitor, decide, learn, or produce.
What agentic visualization is for
Begin with the human purpose, not the chart or the agent.
Agentic data visualization is not one task. A system may help someone discover a pattern, explain a finding, monitor a changing situation, make a decision, or produce and revise a visual artifact. Those goals impose different requirements on autonomy, interaction, evidence, and human control.
An established backbone
Describe the goal, the data, and the method separately.
Brehmer and Munzner’s widely used task typology describes visualization work by why it is undertaken, what data and outputs it acts on, and how encoding and interaction support it. That distinction is especially important for agents: generating a technically valid chart answers “how,” but may still miss the intended human purpose.
Brehmer & Munzner typology ↗Data and output
Which entities, measures, relationships, uncertainty, state, and artifact are in scope?
Means
Encode, select, filter, navigate, derive, annotate, record, compile, or replay.
Human purpose
What the system must help with
Optimize for
Human control
Explain and present
Support a specific account of the evidence.
Journalism, public explanation, and narrative graphics usually have an authorial claim, sequence, and audience. The visualization may offer exploration, but it also has to fit the surrounding story and help a reader understand what the evidence supports.
- Optimize for
- comprehension · integrity · narrative fit · accessibility
- Human control
- high: claim, context, emphasis, and publication
Explore and discover
Help a person form and test questions.
Exploratory analysis begins without one fixed takeaway. The useful system exposes transformed data, alternative mappings, branches, history, and direct controls so the analyst can notice patterns, challenge them, and change direction.
- Optimize for
- iteration · ambiguity · correction · provenance
- Human control
- continuous: steer, inspect, branch, and stop
Monitor and respond
Maintain awareness of changing conditions.
Operational dashboards emphasize current state, thresholds, anomalies, and timely response. Sarikaya and colleagues show why dashboards deserve their own design space: at-a-glance reading, coordinated views, updating data, and shared awareness are not the same problem as free exploration.
- Optimize for
- recency · stable measures · alerts · action state
- Human control
- governed: thresholds, escalation, and response
Compare and decide
Relate evidence to alternatives, targets, or commitments.
Strategic and analytical BI needs trustworthy definitions, fair comparisons, permissions, and enough context to understand tradeoffs. The objective is not merely to surface an interesting pattern but to support a consequential judgment.
- Optimize for
- semantic custody · comparisons · uncertainty · auditability
- Human control
- high where decisions are consequential
Produce, revise, and reuse
Create a durable visual artifact or application.
Authoring tools, coding agents, and scientific systems are judged partly by execution, editability, reproducibility, and delivery. Scientific and 3D work adds specialized coordinate, view, and linkage constraints; interactive applications add browser behavior and state.
- Optimize for
- fidelity · edit locality · reproducibility · behavior
- Human control
- varies with domain risk and reversibility
What is being compared
Next, separate papers, tools, skills, benchmarks, and products.
They overlap, but they are not interchangeable. A paper proposes and evaluates a method. A tool is runnable software. A skill guides a general agent. A benchmark supplies tasks and scoring. A product operates inside a vendor’s data environment.
Object
Claim it makes
What it can establish
Examples
Research papermethod + study
“Here is an approach, and here is how we tested it.”
Usually a prototype plus an experiment. The result applies to the paper’s tasks, models, baselines, graders, and study population—not automatically to production.
Examples: Raiven, nvAgent, DashChatOpen-source toolrunnable code
“Here is software you can inspect or operate.”
The repository shows current mechanisms, interfaces, tests, and failure handling. Code quality and adoption do not by themselves prove better analysis.
Examples: Data Formulator, Lumen, LIDAAgent skillworkflow package
“Here is how a general agent should perform this job.”
Instructions, references, templates, and sometimes check scripts. The skill is not a new model; it changes the model’s working context and required process.
Examples: Vizro flow, OpenAI visualize-data, AntV skillsBenchmarktasks + grader
“Here is a repeatable way to compare systems.”
A benchmark fixes the inputs and scoring rules. It can expose relative strengths while still missing production data, real readers, or consequential decisions.
Examples: DashArena, VisEval, MatPlotBenchCommercial productnative assistant
“Here is an AI feature inside an existing analytics system.”
Its advantage often comes from access to governed fields, measures, permissions, and authoring state. Feature documentation is not an accuracy study.
Examples: Power BI, Tableau, LookerReference system anatomy
Assign information and authority—not agent names.
Six primary systems all generate, execute, and expose some critique route. Four provide a meaningful human control gate. Zero carries an exact configuration through accepted delivery, intended-reader outcome, or later maintenance. The eleven stages are a custody checklist, not one required topology.
Held-system result6/6 technical loop · 4/6 human control · 0/6 downstream chain
The core system papers, plainly
They study different parts of the pipeline.
These eight papers anchor the architecture comparison. Only DashArena is primarily a benchmark. Additional benchmark and training studies are introduced later where they answer the separate question of how quickly the model baseline is changing.
Data Formulator 2
What it is: a chart interface where a person directly picks visual encodings and asks the model for missing data transformations.
Why it matters here: it shows how visible tables, direct controls, branches, and explanations help people steer and verify model work.
Raiven
What it is: a prototype where the model writes a restricted visualization language and a compiler produces linked 2D, 3D, and table views.
Why it matters here: it is strong bounded evidence that a DSL and compiler can remove many coding failures when the requested view is already specified.
NL2Dashboard
What it is: an architecture that stores a dashboard as a compact structured plan and applies small edit operations instead of regenerating everything.
Why it matters here: it tests whether explicit structure improves controllability, edit locality, and token use.
nvAgent
What it is: a pipeline that prepares a database schema, composes a visualization query, executes it, and repairs failures.
Why it matters here: its large VisEval benchmark and component removals help isolate structured composition and execution validation.
DashChat
What it is: a conversational mockup tool with dashboard-pattern retrieval, a restricted dashboard language, structured edits, and history.
Why it matters here: it combines a prompt evaluation with a small study of rapid prototyping and human correction.
NL4DV-LLM
What it is: a method that turns a natural-language question into selected fields, an analytical task, and one or more candidate visualizations.
Why it matters here: it makes mappings and ambiguity visible instead of jumping straight from a sentence to chart code.
PlotGen
What it is: a Matplotlib pipeline with separate numeric, text, and rendered-image feedback passes around generated code.
Why it matters here: it supports multimodal feedback while showing why extra agents and calls need an equal-budget causal test.
DashArena
What it is: a task set, browser executor, and human-calibrated judge for generated interactive dashboards—not an authoring product.
Why it matters here: it evaluates the rendered dashboard and replays the author’s intended interactions, filling a major gap between “it runs” and “it supports the task.”
Terms used later
A short glossary
- Agent
- A model operating in a loop with instructions, tools, and working state—not a synonym for any AI feature.
- IR
- Intermediate representation: a structured, inspectable plan between a request and renderer code.
- DSL
- Domain-specific language: a restricted language for one problem area that a compiler can interpret reliably.
- Semantic model
- A governed description of fields, measures, joins, permissions, and business meaning above raw tables.
- Renderer
- Software that turns a specification or code into pixels and interactive controls.
- Critic
- A model pass that inspects code or a rendered artifact and proposes faults or repairs.
- Trajectory
- A recorded sequence of interactions and resulting states that a browser can replay.
- Held-out
- An evaluation task not used as an example while building or prompting the system.
- Ablation
- A controlled comparison that removes or changes one component to test whether it caused the gain.
- Mixed initiative
- A workflow where natural language and direct human controls both change the artifact.