Skip to content

Curious about AI? Give it a workspace you can check.

Tour 6 of 6

AI is optional. If you use a coding agent, point it at the workspace, not the .ckp.

What the agent works with The same workspace you have. Nothing it runs touches the PLC.

  1. Reads the workspace
    src/plc/
    the ladder as text
    tests/ · notes/
    what you know about the machine

    The ladder text refreshes on every CLICK save.

  2. Works in the offline model
    why · how · step · force
    trace, search, and step the scan
    pytest · check
    the same tests and checks you run

    pyrung's model of the scan. No connection to the PLC.

  3. Proposes files Edits to the ladder text, new tests, comments. All of it sits in the workspace for you to read.

    Preview Changes shows the rung diff.

  4. You accept Select the rungs you want. Copy to Click puts them on the clipboard; you paste them in CLICK.

    Nothing changes until you save in CLICK.

The agent gets the same program, the same tests, and the same command-line checks you have. Start with work that's easy to inspect:

  1. Explain a rung or trace a tag.
  2. Suggest clearer comments and nicknames.
  3. Write a test that pins down existing behavior.
  4. Review a proposed change and run the checks.
  5. Then, if it has earned it, propose ladder changes.

Everything it runs is the same offline model. It has no connection to the PLC, and its ladder changes come back the way yours do: Preview Changes, your selection, then a paste in CLICK.

Install ClickNick Help GitHub

ClickNick never edits your .ckp. Nothing becomes part of the project until you save in CLICK Programming Software. Where ClickNick writes.