aiswmm 0.6.1

Unified CLI for reproducible and auditable Agentic SWMM workflows.

Agentic SWMM Workflow

Agentic SWMM for reproducible stormwater modeling
Codex, OpenClaw, or Hermes Agent + Skills + MCP + SWMM + verification-first workflow + Obsidian-compatible audit

A five-minute EPA SWMM workflow that is auditable, memory-informed, and agent-ready.

Agentic SWMM Workflow is an open-source, verification-first framework for reproducible stormwater modeling with EPA SWMM. It supports automated execution, QA checks, provenance tracking, calibration support, documentation, and modeling memory, while keeping human modelers in control.

The project is designed to work with agent runtimes such as Codex, OpenClaw, or Hermes. Users can describe a modeling goal in natural language, while SWMM execution remains deterministic, inspectable, and artifact-based.

This is not a simple chat-to-SWMM wrapper. The agent can help coordinate the workflow, but model files, SWMM runs, QA checks, plots, provenance records, audit notes, and modeling memory remain visible as reusable artifacts. Modeling memory can summarize repeated problems and propose skill refinements, but accepted changes still require human review and benchmark verification.

Authors: Zhonghao Zhang & Caterina Valeo
License: MIT

Video: Agentic SWMM workflow: introduction and workflow explanation

Paper: Agentic Modelling Pipeline: Reproducible Rapid Stormwater Modelling Management System with OpenClaw

Try it in one command

macOS and Linux:

curl -fsSL https://aiswmm.com/install.sh | bash

Windows PowerShell:

irm https://aiswmm.com/install.ps1 | iex

After installation, launch the runtime with aiswmm. Docker and Python package paths are documented in runtime install options. Release notes: v0.6.1 release README.

Before running a one-line installer, inspect the repository install scripts if you need to review what will be executed. The installer can prompt for an OpenAI API key, or you can configure one later with environment variables; see API key configuration. Do not paste API keys into the aiswmm conversation.

v0.6.1 highlights

• aiswmm now keeps a clearer runtime identity in the interactive terminal, including the aiswmm> prefix and executor banner.
• Interactive outputs use cleaner date-and-case run folders while preserving audited stage folders inside each run.
• The Tecnopolo prepared .inp demo can be run, audited, inspected for plot options, and continued into rainfall/node/output-variable plots from the same active run.
• Plot follow-ups such as Total_inflow J2 MACAO_94_23 now continue from the previous run instead of asking again for model inputs.
• MCP schema discovery is cached and timeout-protected so slow MCP servers do not block the main CLI run/audit/plot path.
• Planner-generated recursive searches such as **.inp are normalized safely, fixing a demo-listing crash path.

Why this project exists

Stormwater modelling is rarely one command. A typical SWMM project can involve GIS preprocessing, rainfall formatting, parameter assignment, network assembly, INP construction, model execution, QA checks, plots, calibration, uncertainty analysis, and reporting.

Agentic SWMM provides a middle path: natural-language orchestration with deterministic SWMM execution, explicit provenance, project memory, and verification-first modelling.

The goal is not to replace SWMM or the modeller, but to make SWMM-based modelling easier to rerun, inspect, remember, and trust.

What makes it different

• Quick onboarding: start from one-line macOS/Linux or Windows installers, with Docker and Python package paths documented separately.
• Agent-guided, SWMM-grounded: agents can coordinate tasks, while model execution stays deterministic, inspectable, and CLI-runnable.
• Modular skill layer: GIS, climate, building, running, plotting, calibration, uncertainty, audit, and orchestration are separated into reusable modules with MCP interfaces where available.
• Verification-first provenance: build, run, audit, and comparison stages emit traceable artifacts before outputs are treated as evidence.
• Supervised skill evolution: audited runs can surface recurring workflow patterns and propose updates to existing skills or new skills, while staying coupled to the current skill-driven framework.

Workflow

The workflow has three connected layers: execution, modeling memory, and controlled skill evolution. Natural-language requests can trigger reproducible SWMM actions; audited artifacts update human-readable and machine-readable memory; repeated patterns can produce skill-refinement proposals that still require human review and benchmark verification.

What a run can produce

• generated or supplied SWMM input files such as model.inp
• SWMM report and binary outputs such as .rpt and .out
• manifests, command traces, QA summaries, and parsed peak-flow metrics
• rainfall-runoff figures, calibration summaries, and fuzzy uncertainty summaries
• audit records: experiment_provenance.json, comparison.json, and experiment_note.md
• Obsidian-ready modelling notes and modelling-memory summaries

Validation snapshot

The repository includes runnable benchmarks and research previews with different evidence boundaries. The README keeps only the index; figures, commands, and boundary notes live in Validation evidence.

Path	What it shows	Evidence boundary
Information-loss-guided subcatchment partition	QGIS-to-Agentic SWMM preprocessing using entropy and fuzzy-similarity concepts from Zhang & Valeo's Journal of Hydrology paper	GIS preprocessing concept, not a calibrated SWMM performance claim
Raw GeoPackage-to-INP benchmark	Public TUFLOW GeoPackage layers converted into SWMM-ready artifacts, QA, and audit	Structured raw GIS path, not arbitrary CAD/GIS recognition
Prepared-input SWMM benchmark	External 40-subcatchment Tecnopolo model execution, plotting, and direct swmm5 comparison	Prepared INP validation path
Prior Monte Carlo uncertainty smoke	Tecnopolo HORTON parameter perturbation and hydrograph envelope preview	Prior uncertainty smoke, not calibration
Optional INP-derived raw adapter benchmark	Raw-like inputs extracted from a public SWMM fixture and rebuilt through the modular path	Adapter handoff check, not greenfield watershed generation

Examples: TUFLOW and Tecnopolo.

Audit and research memory

The audit layer consolidates artifacts, QA checks, and metric provenance into an Obsidian-compatible experiment note. This example catches a recorded peak-flow value that does not match the value re-parsed from the SWMM report source section.

The downstream modelling-memory layer can summarize audited run histories into recurring failure patterns, assumptions, missing evidence, QA issues, lessons learned, and controlled proposals for updating existing skills or creating new skills. Because skills drive the workflow, these proposals stay coupled to the current Agentic SWMM framework and still require human review and benchmark verification before acceptance.

More details: Experiment audit framework and Modeling memory and skill evolution.

Codex / OpenClaw / Hermes ready

Codex can serve as the primary local development runtime for this repository: it can inspect the checkout, run scripts, edit skills, generate audit records, update the local Obsidian vault, and review evidence before claims are accepted.

OpenClaw and Hermes remain compatible orchestration targets, especially for MCP-centered agent runs outside the Codex development environment.

For agent-orchestrated runs, preload the Agentic AI memory package and then use the top-level end-to-end skill:

agentic-ai/memory/
skills/swmm-end-to-end/SKILL.md

The top-level skill defines when to use the full modular path, when to use the prepared-input path, which QA gates must pass, and when to stop instead of inventing missing inputs.

For common prepared-input execution, audit, plotting, and memory summarization, the skill should prefer the unified agentic-swmm CLI. MCP tools remain available for the modular stages and for agent runtimes that need fine-grained tool calls.

More details: Codex runtime path, OpenClaw execution path, Skill installation, and MCP runtime integration.

Documentation map

• Validation evidence - benchmark scope, commands, audit example, and evidence boundaries
• Installation and CLI guide - Docker, local install, Windows options, and CLI examples
• Experiment audit framework - provenance, comparison, and Obsidian note contracts
• Modeling memory and skill evolution - controlled memory-to-skill refinement loop
• Codex runtime path - local development, audit, Obsidian, and evidence-review workflow
• OpenClaw execution path - MCP tool-call sequence for agent runtimes
• Repository map - folder-level walkthrough
• Calibration example - compact calibration support example

Where collaborators can help

Contributions are welcome in additional SWMM case studies, stronger calibration and validation workflows, DEM / land-use / soil / drainage-asset workflows, new MCP tools, QA testing, tutorials, and interoperability with GIS, ML, and hydrologic toolchains.

Contact:

• [e-mail]
• [e-mail]

Citation

GitHub citation metadata is provided in CITATION.cff.

APA repository

Zhang, Z., & Valeo, C. (2026). agentic-swmm-workflow [Computer software]. GitHub. https://github.com/Zhonghao1995/agentic-swmm-workflow

APA manuscript / preprint

Zhang, Z., & Valeo, C. (2026). Agentic Modelling Pipeline: Reproducible Rapid Stormwater Modelling Management System with OpenClaw. https://doi.org/10.31223/X5F47G