flint-chart

🪄 Flint is a visualization language that lets AI agents reliably create expressive, good-looking charts from simple, human-editable chart specs.

Runssource: GitHubhomepageTypeScriptMITcommit 683d5de1ffd0

TypeScript, MIT licensed. The project labels itself: ai agents, charting library, data visualization and mcp server.

flint-chart runs. An Argusic agent installed it in 8 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

After npm install, Node 22 with heap flags, and the rolldown binding fix, npm run typecheck, npm run build, npm run site:build, and npm run test (1739 tests passed) all run cleanly, the MCP server answers HTTP 200 on /mcp and compiles/renders real PNG charts via stdio and HTTP, and the JS library assembles a valid Vega-Lite spec.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
2
last tested
stars
4,580
forks
268
open issues
41
watchers
14
size
62 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing flint-chart, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • tsup DTS worker OOM (ERR_WORKER_OUT_OF_MEMORY) during flint-js build2 minutes
  • Vite 8/rolldown and vitest 4 require Node >=20; container has Node 18 (node:util.styleText missing)2 minutes
  • site build crashed in vite worker without heap flag2 minutes
  • vitest/rolldown: Cannot find module rolldown-binding.linux-x64-gnu.node (native binding not installed)1 minute
  • flint-js dist/index.cjs require("vega") throws ERR_REQUIRE_ESM (upstream packaging limitation)1 minute
  • render_chart options.format=svg returns a PNG artifact, not SVG, in this build
Install time
8 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
npm run test exited 0 (flint-js 73 files/1653 tests, flint-mcp 7 files/86 tests passed); npm run build and npm run site:build exited 0; MCP HTTP POST /mcp returned HTTP 200; stdio initialize returned flint-chart-mcp 0.5.1; compile_chart returned a Vega-Lite spec; render_chart PNGs (4098B/127x341 and 5841B/346x400) decoded by ffmpeg -v error with exit 0
Model tokens used
244,680
Exact commit tested
683d5de1ffd0
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- `npm install` succeeded; `npm run typecheck`, `npm run build`, and `npm run site:build` all exite…
- `npm run test` exited 0 — flint-js 73 files / 1653 tests passed, flint-mcp 7 files / 86 tests pas…
- The MCP server answered HTTP 200 on `/mcp`, completed the stdio MCP handshake (reported `flint-ch…
Fixes applied along the way: used a prebuilt Node 22 binary (Vite 8/rolldown and vitest 4 need Node…
tokens used
244,680
Done. The full mission report is in the `ARGUSIC_RESULT` line above.
Summary of what got verified end to end (all real observations):
- `npm install` succeeded; `npm run typecheck`, `npm run build`, and `npm run site:build` all exite…
- `npm run test` exited 0 — flint-js 73 files / 1653 tests passed, flint-mcp 7 files / 86 tests pas…
- The MCP server answered HTTP 200 on `/mcp`, completed the stdio MCP handshake (reported `flint-ch…
Fixes applied along the way: used a prebuilt Node 22 binary (Vite 8/rolldown and vitest 4 need Node…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 8 minutes to install, slower than the median of the 121 comparable projects Argusic has measured.

Of the 122 ai-agents projects Argusic has installed and timed, flint-chart was the 71st fastest to reach a running state, and 94 of 122 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 8 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.06
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

ai-agentscharting-librarydata-visualizationmcp-server

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/flint-chart.svg)](https://argusic.com/subject/flint-chart)

Questions

Does flint-chart run?
Yes. flint-chart runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test flint-chart?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 683d5de1ffd0. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test flint-chart?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does flint-chart take to install?
8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does flint-chart need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing flint-chart?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does flint-chart compare with the alternatives?
Of the 122 ai-agents projects Argusic has installed and timed, flint-chart was the 71st fastest to reach a running state, and 94 of 122 reached one at all.
Where is the evidence for flint-chart?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion