AI agent for Ignition development

Just make sure you know best practices with scripting before using one of those. I checked that out a little bit and have had it write scripts that do extremely inefficient things (like doing single tag writes inside a loop). On a big enough SCADA that could cause chaos.

That's Gold right there!

In the end, I believe, at least for the next few years, it will be developers who know the Fundamentals, and use AI, will replace the ones not using AI, provided that AI is being used in that Industry.

Eh, I'd use that.
I do my coding in vscode with some help from copilot. If you point it at an intructions.md that says to use jython 2.7, you get pretty good results.
But... you then have to copy/paste everything to your actual ignition lib. That's where things get clunky.
I have plans for making some sort of script that will take a local folder and a container + project name, and will restructure and copy the local files to match the format used by ignition... But I haven't had time for that yet.

I ended up building a workflow around this exact problem.

The main issue for me was the same one mentioned above: generic AI agents can be useful, but they tend to write Python 3, invent fake system.* functions, or miss Ignition-specific context.

What worked better was giving the agent two things:

A dev Gateway API it can use to inspect, dry-run, validate, read logs, and check results.

Skill files for the exact task it is working on, like Jython scripts or Perspective pages.

I personally like using Hermes Agent, but the same idea can work with Codex, Claude, OpenAI, etc. The agent itself matters less than the loop: give it the right Ignition context, let it inspect a dev Gateway, make small changes, validate routes/views/scripts, and collect evidence before trusting the output.

With the Jython and Perspective skills I built through a lot of testing, it has gotten me through a large chunk of normal use cases: Jython scripts, Perspective pages, bindings, components, reusable views, Flex Repeaters, and route validation.

I am also working on Ignition 8.3-specific skills now.

If anyone wants to look it up, search “Ignition AI Skills.” For a demo, search YouTube for “Building Perspective Pages in Ignition 8.1 with AI Agents.” It shows the broader workflow with an AI agent using an API against a Gateway. The API for 8.1 is also available in the website.