AI Assistant Writes and Runs Hydrology Code Directly in Your Browser

An AI-powered assistant that can write, check, and run hydrological computer code inside a web browser has been unveiled by researchers working at the intersection of artificial intelligence and water science. The system, called HydroSuite-AI, was described in a study published in Earth Science Informatics and is designed to tear down one of the most stubborn barriers in modern hydrology: the steep technical learning curve that separates a scientist with a good research question from the working code needed to answer it. In benchmark tests spanning 60 domain-specific tasks, the platform retrieved the correct library functions with up to 95 percent accuracy, suggesting that carefully engineered language model pipelines can meaningfully accelerate environmental research.

The problem the researchers set out to solve is familiar to anyone working in computational science. Hydrological modeling increasingly demands sophisticated process-based models, sprawling data analysis pipelines, and specialized software libraries whose documentation is often fragmented, evolving, or sparse. A hydrologist must typically be both a domain expert and a competent programmer, spending countless hours mastering application programming interfaces, debugging parameter mismatches, and stitching together tools that were never designed to work together. The study’s authors argue that this dual burden diverts time away from the scientific inquiry itself and toward computational housekeeping, a cost that falls hardest on early-career researchers and students with partial coding backgrounds.

HydroSuite-AI attacks the problem by wrapping three open-source web libraries into a single intelligent environment. HydroLang provides modular tools for data fetching, statistical and hydrologic analysis, geospatial processing, and visualization of maps, charts, and tables. HydroCompute brings high-performance computing to the browser, exploiting multithreading and technologies such as WebAssembly, WebGPU, and emerging engines that can even run Python and R code client-side. HydroRTC handles large-scale data sharing and transfer between peers and servers using decentralized WebRTC and WebSocket connections, supporting common hydrological formats like NetCDF, GRIB, and HDF5. Together these libraries form the HydroSuite ecosystem, and the new assistant acts as a conversational bridge between a researcher’s natural language intent and the precise function calls those libraries require.

What distinguishes the system from a standard chatbot is its multi-agent orchestration architecture, organized around a Planner, Worker, and Synthesizer. When a user submits a query, the interface forwards it to a backend that classifies whether the request seeks factual information or executable code. Complex computational requests are decomposed by the Planner Agent into a strict JSON plan of library-specific sub-tasks, which are dispatched asynchronously to specialized Worker Agents. Each Worker is grounded through retrieval-augmented generation, or RAG, in the indexed documentation of its target library, which prevents the model from mixing API syntaxes across packages. Documentation and usage examples are preprocessed into semantic chunks of roughly 1200 tokens with 150-token overlap, embedded at 256 dimensions, and retrieved by cosine similarity, with the 20 most relevant chunks injected into the model’s context window during inference.

The Synthesizer then acts as a lead architect rather than a simple text concatenator. Operating under a strict assembly protocol, it merges the isolated outputs of the parallel workers into a single unified HTML and JavaScript application, normalizes dependencies to match the execution environment, and performs hallucination safety checks. If a requested feature is not supported by the indexed documentation, the system flags the gap and injects a user warning instead of generating non-functional code. Assembled code is finally validated in a client-side Virtualized Execution Environment, which serializes the libraries’ source files into a browser-based Virtual File System, allowing generated applications to run, be edited, and be re-run in an offline-capable, self-contained sandbox.

The evaluation combined three complementary protocols. A qualitative expert assessment rated responses to prompts of varying complexity on a one-to-five scale and labeled failure modes using a hallucination taxonomy adapted from prior research on LLM code generation, distinguishing intent-conflicting errors, context deviations such as inconsistency, repetition and dead code, and knowledge-conflicting errors involving incorrect API or identifier usage. An interoperability case study tasked the system with generating a Collaborative Peer-to-Peer Geospatial Analysis Tool that integrated all three libraries in one page. The synthesized application fetched high-resolution elevation data from the USGS 3DEP program and precipitation grids from CHIRPS, reprojected the rasters into a web-compatible coordinate system using client-side WebAssembly, rendered interactive map layers with HydroLang, and transmitted processed raster buffers directly between users through HydroRTC, all without a server intermediary.

The quantitative benchmark compared four large language model backends across 60 domain-specific tasks verified by the libraries’ lead developers, with tasks phrased using real hydrological terminology such as the Mann-Kendall trend test, the D8 flow algorithm, and the Hargreaves method rather than naming target functions directly. Powered by o3-mini, HydroSuite-AI achieved a Function Retrieval Accuracy of 95.0 percent, though with a mean latency of 23.1 seconds. GPT-4o-mini followed at 86.67 percent accuracy, while GPT-4.1-nano delivered the fastest responses at just under 10 seconds with a lower accuracy of 71.67 percent. The results reveal a clear accuracy-speed tradeoff: heavier reasoning models adhere more faithfully to retrieved documentation, while lightweight models suit interactive use where minor errors can be iteratively corrected. A separate Function Hallucination Rate metric captured responses referencing non-existent or incorrect functions.

Real-world deployment came during WaterSoftHack 2024, a two-week online hackathon supported by a three-year National Science Foundation project and coordinated by Clemson University, the University of Iowa, and CUAHSI. The event began with roughly 120 participants from hydrology departments worldwide before narrowing to ten fellows developing library-based projects. Throughout, HydroSuite-AI served as an interactive assistant, explaining connections between library components, generating code snippets, and providing step-by-step support for building web applications. Participants reported that the tool made documentation easier to access and features easier to apply, and the developers observed that the dominant bottleneck was locating the correct function signature, argument order, and data format across three actively developed libraries before any modeling work could begin.

The authors are candid about limits. Expert evaluation caught cases where the system correctly identified a function such as stochasticRainfallGeneration but misrepresents its input structure, listing required parameters inside a configuration object rather than at the top level as the API actually expects. Advanced multi-step workflows, including a Monte Carlo-ARIMA analysis, received only generic guidance rather than tailored solutions. The system’s performance depends entirely on the quality and currency of its indexed documentation, and the 256-dimensional embeddings may underrepresent the complexity of nuanced hydrological queries. The researchers propose future work including larger embedding sizes, additional code-optimized models, automated verification against library specifications, benchmark tasks phrased for non-expert users, and testing whether the architecture generalizes to scientific software outside hydrology.

Even with these caveats, the study makes a persuasive case that documentation-grounded, multi-agent language model orchestration can reliably automate the function-lookup and boilerplate-generation stage of hydrological software development, with reliability that degrades predictably as task complexity rises. The authors position generated code as an initial working draft that users still edit, test, and validate, with the greatest benefit accruing to students and early-career researchers moving from question to first working implementation. As climate pressures intensify demands on water science, tools that collapse the distance between a research idea and running code may prove as consequential as the models they help deploy.

Subject of Research: An LLM-based multi-agent web environment for hydrological code generation and execution across the HydroSuite open-source library ecosystem

Article Title: HydroSuite-AI: a web-based LLM environment for hydrological code generation and execution for the hydrosuite open-source ecosystem

Article References: HydroSuite-AI: a web-based LLM environment for hydrological code generation and execution for the hydrosuite open-source ecosystem. (n.d.). https://doi.org/10.1007/s12145-026-02222-7

Image Credits: AI Generated

DOI: 10.1007/s12145-026-02222-7

Keywords: HydroSuite-AI, hydroinformatics, large language models, retrieval-augmented generation, multi-agent orchestration, code generation, virtualized execution environment, HydroLang, HydroCompute, HydroRTC, open-source hydrology, web-based computing