Choose Your Workflow¶

Workflow Cards¶

Workflow	Best for	You can do	You should not expect
Program In VS Code	full-time engineering	edit ST, debug, inspect I/O, use visual editors, run tests	operator-only simplicity
Program In Browser IDE	browser-hosted engineering and demos	open `/ide`, edit files, build, validate	zero-admin hosting; someone still has to start the runtime
Automate With CLI / CI / agents	shell, CI, harness, JSON-RPC, Copilot-style flows	build, validate, test, serve agent API, script workflows	rich visual debugging by itself
Maintain An Existing Project	inherited systems and handover work	understand file layout, validate before editing, make safe changes	empty-folder bootstrap speed
Migration While Programming	existing PLC code, vendor habits, or interchange files	pick PLCopen/vendor/library paths and validate compatibility	perfect vendor-runtime cloning

If you want the strongest integrated engineering workflow, use Program In VS Code.
If you were given a runtime URL and want browser-hosted editing, use Program In Browser IDE.
If you want shell, CI, or agent-first automation, use Automate With CLI / CI / agents.
If a colleague handed you a project and left, use Maintain An Existing Project.
If you are bringing code from PLCopen, CODESYS/TwinCAT, Siemens, Mitsubishi, or vendor libraries, use Migration While Programming.