The Claude Code plugin analyzes a legacy codebase, writes a plan you approve, rebuilds or upgrades the code, then runs old and new on the same inputs and reports PROVEN, PARTLY PROVEN or NOT PROVEN. The legacy source is left untouched and a person signs off at set points. The README says to start with one module as a pilot.
For controls and plant IT teams: this targets software codebases (the post and README name no industrial languages), so it fits old in-house tools such as reporting or data-handling code, not PLC logic. Pilot on one small module.
One suite covers Modbus, OPC UA, PROFINET, EtherNet/IP, EtherCAT, PROFIBUS, S7, BACnet, DNP3 and MQTT/Sparkplug, each with a mock device so you can test agent flows before touching a real PLC.
For controls: point an MCP client at the protocol you already run in the field, start with the mock, then flip to the live host when the prompts are safe.
Given 11 demo drawings and site conditions, the AI produced a 61-week plan, crane placement and a 6-day-per-floor cycle. It also found a 25 cm foundation depth mismatch between drawings. The author calls it a starting draft for a construction plan.
With a licensed copy of Logix Designer and its SDK, an agent can propose an online rung edit while you watch. By default it only proposes, and you decide when to test and assemble. The project says this is verified on FactoryTalk Logix Echo, not on a physical controller.
For controls engineers: have an agent propose a rung edit in Studio 5000, then test and assemble it yourself.
