Vue Embedded AnalyticsAgent Framework Overview

Version 3.0.0

The Studio Agent Framework lets users explore data and build or modify dashboards using natural language and an LLM supplied by your application.

AG Studio's Agent Framework is designed to integrate directly with your LLM - AG Studio does not provide any models, servers, or backends. This architecture means AG Studio is:

  • Agnostic: You can integrate with any provider.
  • Private by design: AG Studio sends no data to an AG Grid service. You choose the endpoint that receives it.
  • Economical: There are no additional per-query costs, outside of what your provider charges.
  • Opt-in: It's disabled by default until you explicitly opt-in via module registration.

Example Copy Link

The example below integrates OpenAI's Responses API into an instance of AG Studio that contains a weather report for 39 world cities, from NOAA GHCN-Daily. Open the chat panel and choose one of the suggested prompts, or type a request of your own. The picker beside the send button offers a choice of model.

Key Concepts Copy Link

The Agent Framework provides the pieces your LLM needs to interact with AG Studio: a Harness that holds the conversation, the Agents that decide what to do, and the Tools they act with.

Each of these can be used as-is, customised, or replaced entirely.

Harness Copy Link

The Harness manages the conversation with the user, orchestrates the agents within AG Studio, and exposes what your UI needs to render. Studio ships a harness, built with createAiHarness. You can also write your own.

Within Studio's harness, each agent is paired with a runner, which decides how much of each turn Studio runs for you:

  • Direct LLM Runner - Studio runs the turn loop against a model you reach through an adapter you supply.
  • Client Tool Runner - you answer each turn, and Studio executes the tool calls you leave unresolved.
  • Custom Runner - your loop answers for itself, and Studio drives none of it.

AG Studio does not provide any adapters. Our examples contain an adapter for OpenAI's Responses API which can be repurposed for other providers.

Agents Copy Link

Agents decide what actions to take in response to a user's input. By default, AG Studio provides five agents: Planning, Data, Page, Widget agents, and a Lead agent that co-ordinates them. Each agent carries a set of instructions specific to its task, which can be customised, or replaced.

Tools Copy Link

Tools allow agents to interact with AG Studio. They expose a JSON schema to the LLM that advertises their capabilities, allowing the LLM to request actions on the dashboard. The tool call is then executed and its result returned to the model. AG Studio provides a number of built-in tools that allow agents to read and modify the page, apply filters, and manage agents. You can also define your own custom tools.

What Leaves the Browser Copy Link

Only what your adapter or your endpoint sends. AG Studio composes a request and hands it over; it makes no network calls of its own.

A request typically contains the conversation so far, the resolved instructions, and the tool schemas. A tool schema can include live values, such as an enum of field ids or of widget ids, so your data model's shape can appear in a prompt even when its rows do not. Row values reach the model only when a tool result carries them. execute_query, for example, returns rows as a table for the model to read.

If a field or table name is itself sensitive, remember it may travel in a tool schema. Limit what the agent can see by listing fewer tools, or by writing a tool of your own over a narrower view of the data.

Next Steps Copy Link