Important: AutomationView has no built-in AI and does not write sequences for you. There is no AI agent, AI command, or LLM inside the product. What follows describes using a separate, third-party coding assistant (which you install and run yourself) against your project files. The product simply stores sequences as open Python files that any such tool can read and edit.
AutomationView sequences are plain Python files. Any external AI assistant you run with access to your project folder - for example Claude Code, GitHub Copilot, or Cursor - can read and edit .seq and .machine files directly. This is the same as editing those files in any text editor: nothing is integrated into AutomationView.
Before asking an assistant to write a sequence, give it the automation_machine API reference and your project rules. A common way to do this is a project-context file the tool reads at the start of a session (Claude Code uses CLAUDE.md). This is a convention of the external tool, not an AutomationView feature. See What is a CLAUDE.md file? for a template.
.seq file.Example prompt:
"Write a sequence for a pneumatic cylinder. Sensors: cyl_fwd (forward), cyl_bwd (backward). Output: cyl_extend. The cycle starts on start_cmd, extends, confirms position with a 300ms timer, then retracts."
The assistant produces a .seq file following the rules in your context file. Treat the output as a draft, not a finished sequence.
Generated code is not authoritative. Before relying on it, ask the assistant to self-review:
"Check this sequence against my project rules - look for missing timer confirmations, dual-sensor checks, and any physical output using S/R qualifier."
Then load the file in AutomationView. The Diagnostics panel catches structural issues (deadlocks, unreachable steps, address conflicts). Your own engineering review is still required.
Share the existing file content and describe the change:
"Add an emergency stop step to this sequence. When emergency_stop is active, freeze the sequence in a dedicated step and wait for reset_btn before returning to the initial step."
For machines with repeated equipment (multiple axes, conveyors, or press units):
"Create a dynamic Verin sequence parameterized for forward/backward motion, then create a machine file that instantiates it 4 times: verin_1, verin_2, verin_3, verin_4."
Tip: The more specific you are about variable names and timing constraints, the less you will need to edit the output. If your project already has sequences, point the assistant to them as style references.