02
Program
You describe the rules. Claude writes and edits the program with you.
You know your process. "When the gap is wider, weave wider." "If the part is offset, correct the pick position." You describe the rule in plain language. Claude, connected through our MCP connector, turns it into a working program and edits it with you. You review the code — it's readable. Under the hood it's C#, but you don't need to be a programmer. You need to know your process.
Step 1
Describe what should happen
Open Claude Code, connected to your station through our MCP connector. Tell it what you need: "When the vision model detects a gap wider than 2mm, the robot should oscillate." Claude writes a working program from your description.
Before: hire a robot programmer. Learn a vendor-specific language. Spend weeks writing integration code between camera and robot.
Step 2
Review the code
The generated code is readable C# with comments. You see what it does: reads vision model output, computes waypoints, sends commands to the robot. You can adjust parameters, add conditions, or ask Claude to change it.
Step 3
Compile
Click Compile. The program builds on-device in seconds. Errors show with line numbers — fix them before anything moves. If it compiles, the interfaces are satisfied.
Before: errors found at runtime — when the robot does something unexpected. Or dangerous.
Step 4
Dry run — the cobot moves, the welding machine stays off
You run your program on the station with the welding machine switched off. The cobot moves through the whole program, so you see the path before the first arc.
Step 5
Test on recordings — no cell needed
Take a recording from production. Replay it through your program. See what the program would have done on every frame. Fix something, recompile, replay again. Each iteration: 30 seconds.
Before: need the physical cell available to test. Cell is in production? Wait until the weekend. Each iteration: days of calendar time.