Version 2

Simon Willison launched Datasette Agent on May 21, 2026, a conversational natural-language SQL interface built on top of his Datasette data-publishing tool, framing it as the convergence of his two major open-source projects—the LLM library and Datasette—after three years of parallel development [1][2]. The system uses a plugin architecture; three first-party plugins launched alongside it (charts, image generation, and a Fly Sprites persistent sandbox executor), and an existing community plugin ecosystem with tools like datasette-dashboards and datasette-current-actor provides a broader base for extension [17][3][4]. The live demo runs on Gemini 3.1 Flash-Lite, and quiet development had been underway for at least a week before the public announcement, with the first alpha (0.1a1) released on May 14 [6].

Datasette Agent demonstrates a practical, plugin-based pattern for adding LLM-powered natural language interfaces to existing data infrastructure without replacing the underlying tool. Willison's observation that open-weight models released in the past six months now reliably generate SQLite queries and tool calls [1] suggests the launch timing reflects a genuine capability inflection. His claim that Claude Code and Codex can autonomously write new plugins from a reference repo points toward a self-extending ecosystem that could grow faster than a single maintainer could sustain alone [1].

On May 21, 2026, Simon Willison published the central announcement for Datasette Agent, framing it as the moment his two flagship open-source projects—the LLM library and the SQLite-based data publishing tool Datasette—finally converged after three years of parallel development [1]. The result is a chat-style interface that lets users query any Datasette database in plain English, with the agent translating natural language into SQL behind the scenes. The official Datasette blog simultaneously published its own coverage, describing the project as an extensible AI assistant for Datasette [2].

The architecture is deliberately extensible, and the release landed atop an already-active community plugin ecosystem. Alongside the three first-party plugins that launched with the announcement—datasette-agent-charts, an image generation plugin, and datasette-agent-sprites—an existing base of community-built Datasette plugins includes tools like rclement's datasette-dashboards [3] and cldellow's datasette-current-actor [4], as well as a cookiecutter template for creating new plugins [5]. The live public demo uses Gemini 3.1 Flash-Lite, chosen for its speed, low cost, and reliability on SQLite query generation [1]. Willison notes that Claude Code and OpenAI Codex can both write new plugins effectively when given the reference repository as context, lowering the contribution barrier considerably [1].

Development had been underway quietly for at least a week before the main announcement: the first public alpha, datasette-agent 0.1a1, was released on May 14 [6]. The release cadence then accelerated sharply around the announcement. The charts plugin reached 0.1a1 on May 20 with magnitude-based sequential color shading, interactive tooltips, and a permission check that verifies execute-sql access before running column-name discovery queries [7], then 0.1a2 on May 21 [8]. The core datasette-agent package reached 0.1a3 on May 21, adding 'View SQL query' buttons, suppressed empty reasoning chunks, and improved handling of truncated SQL responses [9]. The datasette-agent-sprites plugin (0.1a0) enables the agent to execute arbitrary commands inside a Fly Sprites persistent sandbox [10][11]—a product that positions itself as 'stateful sandboxes' competing with services like E2B [12][13], and which has drawn its own community discussion around multi-tenant production use cases [14][15].

Willison also made a broader observation about the model landscape: open-weight models released in the past six months are increasingly capable of reliable tool calls and SQL generation against SQLite, positioning Datasette Agent's launch as deliberately timed to a genuine capability inflection rather than a proof-of-concept ahead of its time [1]. Early third-party reception has been positive, with social media commentary calling the project a great win for making data accessible [16], though no independent technical evaluations or critical perspectives have surfaced yet.