Work from the source.
Control logic, I/O configuration, and task definitions live in ordinary files. An agent can explore the same system your engineers do.
The next engineer
shouldn’t start from zero.
Put the machine’s behavior, history, and configuration where your team and your agents can work with them. Build capability that carries forward with every change.
One change. The whole workflow.“Give the start button
“Give the start button
a little more time.”
Follow an illustrative change to the real motor-latch example: increase its start debounce from 200 to 500 milliseconds.
01 / Understand
Start with the whole picture.
Ask your agent to trace the motor-start behavior. It can read the program, inspect the I/O mapping, and follow Git history—all in the same project.
HUMAN
You define the behavior you want.
AGENT
Your agent gathers the context.
Project context
sealin/
├── plc.toml # identity and limits
├── programs/
│ └── Main.st # debounce and motor latch
├── io/
│ └── rio.toml # start, stop, motor mapping
└── tasks.toml # program scheduling
# Follow the history behind the behavior
git log -p -- programs/Main.st02 / Change
Turn intent into a visible change.
“Increase the start debounce to 500 milliseconds.” The agent proposes a small edit to the Structured Text. The exact behavior change is visible in a normal Git diff.
HUMAN
You review the proposed change.
AGENT
Your agent edits the source.
Illustrative diff / programs/Main.st
PROGRAM Main
...
- debounce(IN := start, PT := T#200ms);
+ debounce(IN := start, PT := T#500ms);
seal := (debounce.Q OR seal) AND NOT stop;
motor := seal;
END_PROGRAM
# Review every changed line
git diff -- programs/Main.st03 / Verify
Make the change answer to the tools.
Validate the project, compile an image, and exercise the behavior in simulation. The same command-line tooling is available to your engineers and your agents.
HUMAN
You decide what good looks like.
AGENT
Your agent runs checks and helps investigate.
Validation / an example PLC project
# Validate project configuration
thermite check ./sealin
# Compile the control program
thermite build ./sealin -o sealin.tplc
# Inspect the resolved configuration
thermite inspect ./sealin
# Then test timing and stop behavior
# in your configured simulation environment.04 / Operate
Keep the feedback loop open.
After you approve and deploy the change, observe live values and inspect diagnostics. Commit the change and its rationale so the next person—or agent—can pick up the thread.
HUMAN
You control the deployment decision.
AGENT
Your agent helps interpret the evidence.
Observation / against a configured runtime
# Stream values as machine-readable samples
thermite monitor %IX0.0 %QX0.0 --json
# Inspect runtime and device health
thermite status
thermite diag
# Open the browser diagnostics
thermite web
# Keep the change and its rationale in Git.Bring your own coding agent. ThermitePLC provides the readable project and command-line tools.
A company’s knowledge should compoundPeople move on.
People move on.
Context stays.
A source repository can preserve more than the latest program. Commit messages explain intent. Diffs show decisions. Simulation code captures expected behavior.
An agent can use that context to help a new engineer understand what came before—and make the next change with a clearer view.
THE PROJECT REMEMBERS⑂ main
FOUNDATION
The first working machine.
Logic, I/O mapping, and configuration.
EVOLUTION
A better start sequence.
A reviewed change. Its reason, recorded.
CONTINUITY
A new team. A head start.
The same source. The context to keep going.
An illustration of knowledge carried in Git.
Capability, with continuityA common language
Meet the tools A common language
for people and agents.
Review the actual behavior.
Use Git diffs to understand what changed. Keep the reasoning beside the implementation, where the next engineer can find it.
Close the loop.
The CLI gives both people and agents access to compilation, inspection, monitoring, and diagnostics. Results feed the next decision.
The project is the shared context. Your process decides how changes move from an idea to a machine.
Explore a PLC projectYour next machine starts hereBuild something
Build something
you can build on.
Your control logic. Your project. A PLC license that fits.
Take the next step with ThermitePLC.