Every part is open to your own AI agent.
The project is plain-text files in Git. The gateway is driven from the command line and answers over HTTP and WebSocket. The agent you already use can read and change anything an engineer can. There is no built-in assistant, by design: you choose the agent and the model, and your people review the work and decide what runs.
You HF-1’s controller is on the network at 10.20.4.31, Modbus TCP. The register map is in docs/hf1-registers.md. Add its bath temperature and level to the cast house overview, and show me a draft before anything changes for the operators.
Agent I’ll read the register map, add the device, and put the change up as a draft.
Read docs/hf1-registers.md HR10 bath temperature, HR11 bath level, both sent ×10
Edit config/server.toml device hf1-plc added; the gateway loads it without a restart
Write projects/cast-house/tags/hf1.toml 2 register tags, 2 calculated tags that divide by ten
Edit projects/cast-house/screens/overview/ HF-1 added to index.html and screen.js
Run thermite project draft cast-house hf1 error: Expression tag 'hf1/level': unknown tag reference '{hf1/level_raw}'
Agent The check caught a wrong tag name in one of my calculations. Nothing was published. Fixing it.
Edit projects/cast-house/tags/hf1.toml reference corrected to hf1/level_x10
Run thermite project draft cast-house hf1 published as a draft; serves at /draft/cast-house/hf1/
Fetch /draft/cast-house/hf1/api/tags/hf1/bath_temp 1337.8, quality good
Agent HF-1 is reading in the draft: 1,338 °F and 64.9 %, both good quality. Production is unchanged. Here is the draft screen.
You Looks right. Publish it.
Run thermite project publish cast-house published to production; the previous snapshot is kept
Agent Published. Open operator screens show an update banner. The tag and screen changes are a diff in your repository, ready to commit.
From a request to production, with a draft in between.
An engineer asks for a holding furnace to be added to an overview screen. The agent reads the register map, adds the device, writes the tags, and edits the screen. The gateway rejects its first draft for a wrong tag name, so it fixes the file and tries again.
The engineer looks at the draft with live values in it, then says publish.
Bring your own agent to a live demo and we'll work a change like this one together.
Schedule a live demo →Four ways in. Nothing to install.
An agent that can edit files and run commands already has what it needs. So does an engineer with a text editor and a terminal.
Plain-text project files
Tags, transactions, and queries are TOML. Screens are HTML, CSS, and JavaScript. Devices and gateway settings sit in one configuration file.
projects/cast-house/tags/hf1.toml Git
The project source is a directory in your repository. Every change is a diff, and history and review happen in the tools your team already uses.
git diff projects/cast-house The thermite command line
Create a project, put a draft on the gateway, publish it, and take it down again. Commands print plain text and exit non-zero when a check fails.
thermite project draft cast-house hf1 HTTP and WebSocket
The gateway answers with JSON: tag values with quality and timestamp, active alarms, device status, and its own log. Live values stream over WebSocket.
GET /p/cast-house/api/tags/hf1/bath_temp The everyday work of a SCADA project.
Because nothing is locked inside a designer application, the work an engineer does by hand is work an agent can do too.
Add a device and its tags
Add the device to the gateway configuration, which loads without a restart, and write the tag files from your register map.
Build and change screens
A screen is a web page with a small library for live values, so an agent writes it the way it writes any HTML, CSS, and JavaScript.
Check its own work
Publish a draft, read the live values back from the draft, and fix what the gateway's checks reject before anyone is asked to review.
Look into a connection
Read device status and the gateway log over HTTP to see which device is disconnected and what the gateway recorded about it.
Write queries and transactions
Named queries and transaction groups are files beside the tags, written and reviewed the same way.
Explain the project
Everything that defines the project is readable text, so an agent can answer where a value comes from, what a limit is set to, and what changed and when.
Review the change before it runs.
How much an agent does on its own is your decision. Give it the repository and keep publishing with your engineers, or let it draft and publish on a test gateway. Either way the work arrives as something a person can read.
- Read the diff
- The agent's work is a set of file changes in your repository. Review it in a pull request like any other change.
- Look at the draft
- A draft is served at its own address beside production and reads live values. Drafts never raise alarms, and operators see nothing until you publish.
- Publish when you decide
- Publishing is one command. The previous snapshot is kept, and open operator screens show an update banner.
- Set what the gateway accepts
- With authentication on, writes through the gateway's interfaces are checked against each project's roles.
Bring your own agent to a live demo.
We'll start a gateway, hand your agent a project, and work a change together. Or start the trial and try it on your own machine: no account needed.