Control Seat V0.1.3 — AI that understands your data
V0.1.3 teaches the AI to read your history. The assistant can now pull raw points, aggregates, or the last N readings from any tag to answer questions like "was the pump running hot yesterday afternoon?" — right from the same popover you use to edit a page or wire up a flow. The flow AI editor also got a full multi-turn chat experience, and tag paths switched to a cleaner / separator across the board.
What's in V0.1.3
The AI can now query your data
The assistant gets direct access to your historian, so you can ask questions about what actually happened and it can look up the answer instead of guessing. Three modes cover the common shapes:
- Trend over time — min / max / average / count per time bucket, for questions like "what was pump RPM averaged per minute over the last hour?"
- Exact-moment lookup — raw points in a time range, for questions like "show me every temperature reading in the 30 seconds before the high-temp alarm at 2:47 PM"
- Most recent values — the last N readings for a tag, for questions like "what are the last ten readings from the tank level sensor?"
Time ranges accept natural shortcuts — "last 5 minutes", "last 2 hours", "yesterday" — alongside exact timestamps. When numeric values carry quality indicators (good / uncertain / bad from OPC-UA sensors), the AI sees them too, and will flag readings that aren't trustworthy before drawing conclusions from them.
The data-query tools are wired into both AI editors — the page editor's AI popover and the new flow AI popover — so you can ground any design decision in real data, not guesses.
A much smarter flow AI editor
The flow AI got a ground-up rewrite and now runs the same streaming agent loop the page AI uses. Working with it feels like a real conversation about the flow you're building:
- Multi-turn chat — the popover keeps conversation history, so you can follow up with "now add a throttle before the Notify" without re-describing everything from scratch.
- Nodes appear as the AI creates them — instead of a long pause and a big before/after, you see each new node pop onto the canvas live while the AI explains what it's doing. Edges light up as they're connected.
- Automatic layout pass — after adding nodes, the AI tidies the canvas so new nodes align with what's already there and don't overlap existing logic.
- Stop button — cancel a turn mid-flight (great when the AI is going down the wrong path) and the flow is left in the last stable state.
- Live status messages — the popover shows which tool the AI just ran ("searching node types", "configuring Threshold node") instead of a generic spinner.
- Retry on failure — if a tool call fails, the AI gets the error back and tries a different approach instead of giving up.
Under the hood, the flow AI can now add and remove nodes, reconfigure node parameters, create and remove connections, move nodes on the canvas, and even trigger a test run — all in a single reviewable turn.
Tag paths now use / instead of .
Tag paths across Control Seat now use forward slashes:
Before: default.pump.speed
After: default/pump/speed
You don't need to do anything — an automatic migration converts every saved tag reference (in dashboards, flows, charts, alarms, historian queries, and bindings) when the update deploys. Tag names that happened to contain a slash are preserved correctly through the migration.
Going forward, the tag picker, flow node config fields, binding editor, and chart data sources all show and accept / paths. If you've got docs or scripts you wrote yourself that reference tags by path, those are the ones worth updating. Our docs have been refreshed to match.
"Query tag" is now "Table tag"
The multi-row tag type introduced in V0.1.2 was confusingly called a Query tag — but every datasource-backed tag is technically a query. It's now labeled a Table tag in the tag form, which is what it actually produces: a table of rows for data table components to bind to.
No action required — existing tags keep working, only the label in the UI changed.
Viewer mode polish
A round of fixes around read-only / viewer users:
- Permission-aware gateway settings — viewer users now see settings pages for AI preferences, alarms, API connections, database connections, and project management in a read-only state. Write buttons are disabled with a "Requires configure permission" tooltip so it's clear why they're greyed out, instead of letting a viewer click through and get a server error.
- No more unsaved-changes prompts for viewers — navigating between pages in viewer mode no longer triggers the "you have unsaved changes" dialog when you haven't actually edited anything.
- Dark-mode contrast — the password requirement indicators on the sign-in / password-reset flows now have proper contrast in both light and dark themes.
- Data table selectable in the editor — fixed an issue where data table components were hard to click-select on the canvas.
More AI and flows work landing soon. Read the Flows docs or get in touch for a demo.