Microsoft makes Flint-interactive available for creating interactive charts with AI agents
Flint-interactive extends Flint with descriptions of chart interactions. Through Flint-MCP and MCP Apps, an agent can create and display an interactive chart directly in the conversation. Developers can connect charts to tables, text, and application controls.
Microsoft introduced Flint-interactive, a language that extends Flint to support the creation of interactive data visualizations. Through Flint-MCP and MCP Apps, an agent can create an interaction_spec describing the desired interactions alongside the chart specification and render the result directly in the conversation.
According to Microsoft, the compiler translates user interactions into semantic events that capture the meaning of a user selection. These events trigger operations that update the chart. The company says separating interactions from rendering should make more complex visualizations easier to create and maintain.
Flint Interactive Canvas supports integration into applications. An application can respond to chart events by filtering a table, changing another chart, or updating its state. A programmatic API also allows developers to define custom responses, such as highlighting a selected country and adding its name, without directly manipulating elements of a particular rendering system.
Why it matters
A chart selection can serve as input for further data exploration: updating a related view or linking the chart to text. The same mechanism can be used both in a conversation with an agent and when developing dashboard applications.
Two audiences, two different impacts
What this means
For individuals
Users can specify both the chart content and the desired interactions to the agent, then explore the resulting visualization directly in the conversation.
For a business
Development teams can connect charts to tables and application controls through semantic events. According to Microsoft, this can reduce the need to work with rendering details when creating and maintaining interactions.
DevelopmentCheck the original
Event sources
only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.