frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Open in hackernews

Show HN: Microsoft releases Flint, a visualization language for AI agents

https://microsoft.github.io/flint-chart/#/
54•chenglong-hn•1h ago
Data visualizations are the bridge between user and data.

But building AI agents that can generate visualizations reliably can be very tricky:

- simple chart specs can be reliable, but generated charts are often of low quality due to reliance on system defaults; - complex chart specs with explicit details can produce good-looking charts, but they are verbose and agents can struggle with reliability

We figured out it is a limitation on the language issue (not just AI capability thing) -- current visualization languages are a bit too low-level for AI agents, requiring them to explicitly make visual decisions that are supposed to be handled by a good compiler. Flint is a visualization intermediate language to address this issue, allow AI agents to solve this last-mile human-agent interaction problem. It provides a simple semantic-type based specification, and contains a layout optimization engine that can produce good-looking charts (filled with derived low-level details) from simple high-level specs. The result is also very human understandable and adaptable. Flint powers data formulator for generating visualizations (another open source project from microsoft https://data-formulator.ai/).

Flint is available open source, and we built a MCP server that you can directly plug flint in your favorite agent app to play with data.

Comments

chenglong-hn•1h ago
Project page: https://microsoft.github.io/flint-chart/

MCP setup: https://microsoft.github.io/flint-chart/#/mcp

ietcd•1h ago
https://github.com/scicloj/kindly

but enterprise

theK•1h ago
> requiring them to explicitly make visual decisions that are supposed to be handled by a good compiler

Isnt graphviz there for the same reason?

Edit: I see it is using JSON as the declaration language, I am OK with llms being "good at json" but a syntax also consumable by humans it is not!

chenglong-hn•55m ago
In fact, Json as a common language for human in visualization has been around for a while! The benefit of declarative grammar is that users can effective manipulate specs through UI (drag and drop, clicks).

Btw, Flint is intentionally designed to allow agent skip low-level params like scale, axe, zero, step size etc (which are extremely crucial for "GOOD-looking") and they are dynamically optimized by the compiler. So AI agents can have a easier time.

theK•35m ago
> Json as a common language for human in visualization has been around for a while

Plant, Mermaid, Graphviz are all declarative textual representations designed for human authoring, JSON is made for tools. Its not a criticism just a statement that if interop across agent and human was intended this is not the simplest option.

chenglong-hn•19m ago
right, in fact many small models still struggle with following json, some new forms are also needed
animal_spirits•1h ago
It compiles into Echarts, but echarts already has a JSON co figuration spec
chenglong-hn•59m ago
It's more like a simple high-level spec to make it easier. The idea is that you don't have to fill position / axes details just to make the chart work. The compiler has a bit of magic of using semantic types to optimize what parameters will be set in ECharts.

In some composite chart examples, the good-looking echart spec is like 5x longer than the simple Flint one!

FailMore•1h ago
The charts are very nice, and I think the visualisation layer for LLMs is a very interesting problem.

I’ve been building https://smalldocs.org for this exact reason. It’s an office suite for AI agents - but my main use case is giving a cli based LLM the canvas to express itself - charts, mermaid diagrams, etc. I’ve extended it a bit further to be a format for all types of work so the agent can embed slides and spreadsheets in a document.

Sample document: https://smalldocs.org/blogs/what-is-a-smalldoc

Source: https://github.com/espressoplease/smalldocs

giancarlostoro•1h ago
> mermaid diagrams

I'm terrible at diagrams, so I gave GPT very generic descriptions of one of our project, to convert in to that mermaid style, then for Lucid I pasted it in there, and had a visualization of what I needed. Worked out nicely.

FailMore•27m ago
Yep I find them to be very useful for explaining a system.

They can do a lot of cool things! Mermaid gallery here: https://smalldocs.org/s/xZrc-lNW1kbXpoIuU3l_ky#k=-0ehGe2B-hR...

altmanaltman•21m ago
interesting how you don't discuss literally anything about the project actually posted and spam your thing. Not pointing you out, seen many other comments like this on HN but always felt a bit weird about them
neomantra•51m ago
This is cool to see from a research team. A few weeks ago I was exploring a similar idea with ntcharts, where a user or LLM can specify a chart in a Golang or JSON object...

and then that spec would be rendered either to a Bubble TUI via NTCharts or to HTML/SVG via ECharts. That Echarts HTML could be naturally served by a Golang http service.

But Flint goes much deeper with semantic layers and settings optimizations. Perhaps a NTChart, or whatever terminal chart, could be a rendering target? I'll add it to the list to explore...

https://github.com/NimbleMarkets/ntcharts/blob/spec/spec/REA...

chenglong-hn•34m ago
This is fun! We started thinking it would just be an engineering task in the beginning, but doing a solid intermediate language turned out to be a research project (the paper will be out soon).

Also, I find NTChart very fun, maybe we should add NT chart to the list of compilation backend for Flint so it works in the library. Putting a reminder here: https://github.com/microsoft/flint-chart/issues/45

santiagobasulto•41m ago
Forget AI agents, this DSL is better even for humans. Cool project!
chenglong-hn•23m ago
For AI agents and Humans :)
kveykva•38m ago
Is there a specific explanation about how this is better or different than vega itself? https://vega.github.io/vega/docs/specification/

My understanding is that Vega was already an expressive DSL for visualizations and its probably already well spread through LLM training data.

chenglong-hn•30m ago
Vega was a high-level language in the past for human, but now they can be a bit too low-level for AI agents! AI agents have to write a lot of low-level params just to make charts looking good, and the result is that programs are hard to write reliably for AI agents.

Flint is a higher-level abstraction, with simpler much shorter spec, and the compiler derives low-level decisions so that charts are looking good.

So: flint lets agent write short program that achieving good looking charts that had to be done with lengthy program in the past.

dvt•34m ago
This is pretty crazy, literally built something almost exactly like this for a project I'm working on (a local-first AI agent that does work on folders while you sleep). Basically going from JSON "Lego blocks" to full reports (including charting, though a subset of what Flint offers). And with post-generation validation and retry steps.

Functions extremely well and the result is a very clear (and consitent) human-readable "output layer." Cool idea, fun to see people converging on similar concepts in the space.

chenglong-hn•29m ago
That's awesome!

I find that besides training better models, designing new language for agents is also a super viable paths to improve their performance!

hideout_berlin•21m ago
lame
nrub•9m ago
> simple chart specs can be reliable, but generated charts are often of low quality due to reliance on system defaults; - complex chart specs with explicit details can produce good-looking charts, but they are verbose and agents can struggle with reliability

N of only a few of us working on an analytics agent, I don't think we've been finding this to be the case. We've been impressed with just how good LLMs (even smaller open weight models) are at using Python and R for visualization. Often any shortcomings go away if we iterate a bit to about ambiguity. Are there any threads of research that could better support this claim or highlight where issues might be?

Show HN: Microsoft releases Flint, a visualization language for AI agents

https://microsoft.github.io/flint-chart/#/
57•chenglong-hn•1h ago•21 comments

Show HN: Follow London Trains in 3D

https://ride.nexttrain.london/
97•mgranados•4d ago•43 comments

Show HN: Agent Draw: An agent draws while you talk, built on TLDraw

https://techstackups.com/articles/tldraw-agent-draw/
4•jameswhitford•2d ago•0 comments

Show HN: Davit, a Apple Containers UI

https://davit.app
374•xinit•1d ago•95 comments

Show HN: Foreman, a self-hosted LLM gateway for cost aware model routing

https://github.com/Northwood-Systems/foreman
2•AndrewLiu96•1h ago•0 comments

Show HN: Monogram, AI app with on the fly generation

https://www.monogram.ai/
8•edouard1234567•1h ago•3 comments

Show HN: Requirements Engineering with Formal Verification

https://fizzbee.ai/
9•jayaprabhakar•1h ago•0 comments

Show HN: Hover over your UI element to get its exact location in code

https://loerei.github.io/HoverSource/
2•Loerei•1h ago•1 comments

Show HN: Kastor – Terraform-style specs for AI agents

https://github.com/weirdGuy/kastor
29•weirdguy•3h ago•17 comments

Show HN: Rowboat – Open-source, local-first alternative to Claude Desktop

https://github.com/rowboatlabs/rowboat
209•segmenta•1d ago•90 comments

Show HN: Neil the Seal Game

https://neiltheseal.app/
80•dalemhurley•3d ago•66 comments

Show HN: Chiptune Radio

https://chiptune-radio.alephvoid.com/
71•bootbloopers•18h ago•15 comments

Show HN: Maps for e-scooters (hills and battery routing)

https://battmap.com
2•thepaulthomson•3h ago•2 comments

Show HN: Pug.sh – open-source product analytics

https://pug.sh/
9•BajajScooter•6h ago•5 comments

Show HN: Free Mermaid Diagram Editor

https://moxiedocs.com/mermaid-diagram-editor
49•ghosts_•19h ago•12 comments

Show HN: PostgreSQL performance and cost across 23 EC2 instance types

https://postgres.saneengineer.com
94•anivan_•1d ago•19 comments

Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens

https://github.com/kklimuk/docx-cli
69•kirillklimuk•1d ago•30 comments

Show HN: Fast, native Mac file manager (filters, fuzzy find, 9 MB, no Electron)

https://whimfiles.com
97•whimbyte•1d ago•68 comments

Show HN: Halo – open-source, tamper-evident runtime evidence for AI agents

https://github.com/bkuan001/halo-record
37•brian_kuan•1d ago•23 comments

Show HN: Pretend to Vibe Code, but Meditate

https://tomreinert.de/no-effort/
5•tom2948329494•2h ago•4 comments

Show HN: your website as a TUI, over SSH right now

11•keepamovin•19h ago•5 comments

Show HN: Turbo – An open-source, fast HTTP server with a real-time config GUI

https://turbo.okzgn.com
8•okzgn•19h ago•2 comments

Show HN: Pulpie – Models for Cleaning the Web

https://usefeyn.com/blog/pulpie-pareto-optimal-models-for-cleaning-the-web/
101•snyy•2d ago•25 comments

Show HN: Ghostmeet – Self-hosted meeting transcription and summaries

https://ghostmeet.sshlab.dev/
17•swq115•17h ago•7 comments

Show HN: I built an AI spritesheet generator for game developers

https://www.autosprite.io
4•autosprite•20h ago•0 comments

Show HN: OCR Buddy: local browser OCR for code, formulas (LaTeX) and tables

https://github.com/Fanfulla/OCR-buddy
6•Fanfulla•21h ago•0 comments

Show HN: Jot, a menu bar app that catches a thought before it's gone

https://jot.arunbrahma.com
5•masterbrewer•12h ago•5 comments

Show HN: Codex-profiles – isolated Codex CLI/Desktop profiles

https://ducksss.github.io/codex-profiles/
3•chaipinzheng•12h ago•0 comments

Show HN: Baerly-storage, a document DB that runs per request, no DB server

https://github.com/Gusto/baerly-storage
17•baerbaerbaer•1d ago•1 comments

Show HN: Context Warp Drive – Deterministic context folding for AI agents

https://github.com/dogtorjonah/context-warp-drive
10•Dr_Jonah•1d ago•5 comments