mlsanityData to 14 Oct 2026

A Query Engine for the Agents

arXiv 2605.27785 ↗First posted 27 May 2026cs.AI cs.DBcited by 0

On the map: LLM reasoning → Reasoning for agents, planning and code

also in 1 more
Abstract (arXiv)

The fastest-growing data in production today is unstructured text: agent traces, chat logs, reasoning chains, model outputs. People want to analyze it, and the questions worth asking ("show me where the agent got confused") cannot be answered by SQL alone, since text is not queryable without a model in the query path. The natural place this analysis is happening is the new class of AI applications (Claude Code, Cursor, Claude Desktop, in-browser agents) that run client-side and host both a human user and an LLM agent in the same process. These applications increasingly want to work with data, but the lakehouse read path has been hard to use from a JS runtime: Spark, Trino, and managed warehouses do not fit there. To build this new kind of AI data application, three properties of the engine become first-order: a JS-native distribution that drops into the runtime the application already runs in, a bundle small enough to ship inside a cold tab or per-turn agent sandbox, and a way to interleave analytic operators with model-based interpretation of text. We present Hyperparam, three open-source JavaScript libraries (Hyparquet, Squirreling, Icebird) totaling under 70 KB, that read Parquet and Apache Iceberg directly from object storage and meet the third property with per-cell, async-native SQL execution, so expensive cells fire only when downstream operators demand them. Squirreling runs LLM-shaped async UDFs over 300x faster than DuckDB-WASM on filter-bounded queries (and 192x on sort-bounded queries) and completes a ten-task agent analyst suite at two-thirds lower cost. We argue that data engineering as a discipline needs to update for the AI-native client applications now in production and the agents that work alongside their users.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Placed in Reasoning for agents, planning and code, one of 17 directions in LLM reasoning. Builds on 5 of its 19 references that are in the map. First posted on arXiv 27 May 2026.

Builds on

5 of 19 references.

References · 5

  1. 2024Who Validates the Validators? Aligning LLM-Assisted Evaluation of LLM Outputs with Human Preferencescited by 144
  2. 2020A Survey on Automated Log Analysis for Reliability Engineeringcited by 50
  3. 2025Supporting Our AI Overlords: Redesigning Data Systems to be Agent-Firstcited by 32
  4. 2024UQE: A Query Engine for Unstructured Databasescited by 21
  5. 2025Trustworthy AI in the Agentic Lakehouse: from Concurrency to Governancecited by 5

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026GenDB: The Next Generation of Query Processing -- Synthesized, Not Engineered
  2. 2025LLM/Agent-as-Data-Analyst: A Survey
  3. 2026DataClawEval: A Benchmark for Data Engineering Agents in Real Industrial Harness
  4. 2025Rethinking Query Optimization for Multi-Agent Systems [Vision]
  5. 2025BAPPA: Benchmarking Agents, Plans, and Pipelines for Automated Text-to-SQL Generation
  6. 2024A Survey on Large Language Model-based Agents for Statistics and Data Science
  7. 2024LAMBDA: A Large Model Based Data Agent
  8. 2025Large Language Model-based Data Science Agent: A Survey