Ask an LLM to draw a chart and you usually get a wall of Vega-Lite config, half of it broken — flipped axes, dead scales, labels stacked on top of each other. Charts are the last mile where agents still look dumb. Microsoft Research’s answer is Flint, an open-source intermediate language that sits between the agent and the rendering engine.
What it actually is
Flint is a compact, declarative chart spec. The agent says what the data is, what type of chart it wants, and what each field means — Flint ships 70+ semantic types like Rank, Price, Temperature, and Country — and the compiler derives the scales, spacing, and layout. One Flint spec renders natively as Vega-Lite, ECharts, or Chart.js. It’s short enough that a human can hand-edit it, which is the whole point.
The agent hook
There’s an MCP server, flint-chart-mcp, so any agent inside a chat or coding tool can create, validate, and render charts directly; a JS/TS library does the compiling. Show HN put it on the front page at 283 points, and the argument there was mostly whether this becomes the default chart layer for the agent era. Betting on a small, semantic spec instead of raw config is the right instinct.
You Might Also Like
- Google A2ui Agent to User Interface Finally a Standard way for ai Agents to Show you Things
- Agent Reach Hits 12k Github Stars by Solving ai Agents Biggest Blind Spot
- Agent Skills Addy Osmani hit 8600 Github Stars by Forcing Coding Agents to act Like Senior Engineers
- Agent Builder by Thesys When ai Agents Stop Talking and Start Showing
- Openfang Just Dropped and its Already the Hottest Agent os on Github
Top AI Product 
Leave a comment