# AI agent for Ignition development **URL:** \ **Category:** General Discussion\ **Created:** [July 13, 2025, 3:31pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411 "2025-07-13T15:31:54Z")\ **Posts on this page:** 12\ **Page:** 2
**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\ **Post date:** [July 21, 2025, 1:22pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/21 "2025-07-21T13:22:40Z")
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. ---
**Author:** ![saqib.shafin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/saqib.shafin/32/67615_2.png) [@saqib.shafin](https://forum.inductiveautomation.com/u/saqib.shafin)\ **Post date:** [July 23, 2025, 4:30pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/22 "2025-07-23T16:30:05Z")
That's Gold right there! ---
**Author:** ![saqib.shafin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/saqib.shafin/32/67615_2.png) [@saqib.shafin](https://forum.inductiveautomation.com/u/saqib.shafin)\ **Post date:** [July 23, 2025, 4:48pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/23 "2025-07-23T16:48:21Z")
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. ---
**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\ **Post date:** [July 28, 2025, 9:56am UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/24 "2025-07-28T09:56:07Z")
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. ---
**Author:** ![Rudy.Ind.Automation](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@Rudy.Ind.Automation](https://forum.inductiveautomation.com/u/Rudy.Ind.Automation)\ **Post date:** [July 9, 2026, 2:16pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/27 "2026-07-09T14:16:36Z")
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. ---
**Author:** ![ji.munoz](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@ji.munoz](https://forum.inductiveautomation.com/u/ji.munoz)\ **Post date:** [July 17, 2026, 9:35am UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/28 "2026-07-17T09:35:10Z")
> **[Hello AI, Meet Ignition: Leveraging LLMs in the Ignition Ecosystem](https://inductiveautomation.com/resources/icc/2025/hello-ai-meet-ignition-leveraging-llms-in-the-ignition-ecosystem)** > > Explore how Artificial Intelligence (AI) and Large Language Models (LLMs) can enhance the Ignition platform in practical, effective ways. This session will introduce approachable methods for integrating LLMs into your industrial systems — no advanced... This is incredibly interesting, Kevin. I’ve started going through the Iggy repository, and it has honestly blown my mind—not only because of what it already does, but because of where the same approach could go next. I’m working on something closely related: a specialized harness and IDE-like environment for creating and modifying Ignition Perspective projects with AI. Seeing Iggy already operating inside the Ignition ecosystem makes me think the next step could be bringing that intelligence directly into the development workflow. For example, could an assistant like Iggy eventually be integrated into the Designer, or connected to a dedicated IDE, where it understands the project structure and helps developers create views, configure bindings, work with tags and scripts, preview changes and validate the result? I already have an early prototype of this approach partially working, and I’d be very happy to show you what I’ve built if you’re interested. I’d also really like to dig deeper into the technical decisions behind Iggy, exchange ideas, and contribute or help test anything around this direction. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 17, 2026, 11:27am UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/29 "2026-07-17T11:27:34Z")
Iggy was an exchange resource built by sales engineering. > [@Kevin.Herron](#): > > Sounds neat in theory. I wouldn't hold your breath. > > Don't get me wrong, there's a handful of us who are AI enthusiasts and we're excited about what is or might be possible, and we're watching the space. But it's moving too fast right now to realistically do anything. ^ This is no longer representative of our AI position. I can't really say anything more. Come to ICC or watch the keynote/talks after 🤷‍♂️ ---
**Author:** ![ji.munoz](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@ji.munoz](https://forum.inductiveautomation.com/u/ji.munoz)\ **Post date:** [July 17, 2026, 12:48pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/30 "2026-07-17T12:48:47Z")
So, in roughly a year, we’ve gone from “we can’t realistically do anything” to “I can’t really say anything more.” ![Doakes Looking](https://static.klipy.com/ii/4493325008d34b7bf8cd6813cd5c1619/20/dc/7ynObeUhGgS5.webp) Blink twice if IgnitionA is working on AI inside the Designer, or on some kind of development assistant And if you actually like my prototype, you could invite me to icc… or at least sneak me an early preview of whatever has suddenly made IA’s AI position so difficult to talk about. Deal? ![Tim Robinson: We Got A Deal Or Not?](https://static.klipy.com/ii/c3a19a0b747a76e98651f2b9a3cca5ff/94/3d/9m4mp4k4.webp) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 17, 2026, 1:06pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/31 "2026-07-17T13:06:40Z")
> [@ji.munoz](#): > > So, in roughly a year, A year is an eternity in the AI world 🙃 I wrote that in July 2025. Anybody paying attention knows there was a major step change in ~November 2025 when Opus 4.5 was released, and the models, from all providers, have only gotten more capable since then. ---
**Author:** ![ji.munoz](https://avatars.discourse-cdn.com/v4/letter/j/e19b73/32.png) [@ji.munoz](https://forum.inductiveautomation.com/u/ji.munoz)\ **Post date:** [July 17, 2026, 1:30pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/32 "2026-07-17T13:30:15Z")
Fair point—the models changed fast. But the change from “we can’t” to “I can’t say” is what caught my attention . So… AI inside the Designer or a Perspective copilot? Blink twice 👀 Also if opus was a change what about fable and gpt sol cause thats another step. ---
**Author:** ![elijah.roberts](https://avatars.discourse-cdn.com/v4/letter/e/a6a055/32.png) [@elijah.roberts](https://forum.inductiveautomation.com/u/elijah.roberts)\ **Post date:** [July 17, 2026, 6:10pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/33 "2026-07-17T18:10:06Z")
This makes me excited and yet a bit disappointed as my side project may not see the light of day if inductive releases a native designer ai. Still excited though for ICC. ---
**Author:** ![Rudy.Ind.Automation](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@Rudy.Ind.Automation](https://forum.inductiveautomation.com/u/Rudy.Ind.Automation)\ **Post date:** [July 23, 2026, 10:58pm UTC](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411/34 "2026-07-23T22:58:43Z")
Im exicited for this, im using skills that I built and work pretty great. I can imagine what you guys release will be much better. [Previous page](https://forum.inductiveautomation.com/t/ai-agent-for-ignition-development/108411.md?page=1)