One router, the right runtime behind it
2ot.exe is the stable execution surface underneath automation scripts and LLM harnesses. It resolves the configured workspace and routes each operation to the compiler, protocol service or vendor-specific executable that actually owns the work.
Designed to sit behind your preferred harness
A script, CI job, internal engineering tool or LLM harness can invoke the same routed commands and consume their structured results. Engineers choose and control that higher-level workflow. Running 2ot directly remains useful for setup, inspection, debugging and advanced manual work, but it is not the only interface to the toolchain.
Vendor names are usually optional
Once a workspace is configured, commands such as 2ot pull, 2ot push,2ot build and 2ot status can resolve the correct vendor runtime from workspace metadata. A harness can use an explicit 2ot tia ...,2ot codesys ... or 2ot twincat ... route when an operation is vendor-specific or workspace inference should be bypassed.
A compact execution flow
A harness can inspect what is installed, confirm the workspace, run the fast compiler loop, then hand off to the vendor runtime only when an authoritative build is needed.
See which routed capabilities are installed on this machine.
Confirm the workspace resolves to the expected integration runtime.
Run the compiler-only diagnostic loop before touching vendor software.
Hand off to the configured vendor runtime for the authoritative target build.
Workspace-facing commands
These are the stable commands automation scripts and LLM harnesses normally invoke for workspace-level work. The router keeps that interface stable while the implementation can live in a dedicated leaf executable.
| Command | Purpose | Routing behavior |
|---|---|---|
| 2ot link | Workspace binding | Associates a text workspace with its vendor project and routing metadata. |
| 2ot status | Workspace status | Reports the effective workspace and integration state through the configured runtime. |
| 2ot pull | Text extraction | Routes to the configured vendor runtime and materializes project-side changes into the workspace. |
| 2ot push | Code injection | Routes workspace edits back into the configured vendor environment. |
| 2ot build | Authoritative build | Runs the configured vendor toolchain when an exact target build is required. |
| 2ot open | Project launch | Opens the configured vendor project through its integration runtime. |
| 2ot rm | Object deletion | Removes supported project objects through the configured vendor integration. |
Fast diagnostics
The fast path stays inside the 2ot compiler instead of launching vendor software. It is the preferred low-latency diagnostic route for scripts and agent harnesses before an authoritative vendor build.
Compiler lowering and emission
The transpile route enters the compiler pipeline directly for CST/HIR/TIR analysis, target-aware lowering and output emission without making a vendor runtime the public API.
Explicit vendor and compiler-driver routes
Explicit routes expose operations that only make sense for a specific engineering environment or compiler driver. They are still reached through the same 2ot router.
Siemens TIA Portal Openness, workspace, process and project operations.
CODESYS project synchronization, build and runtime-specific operations.
TwinCAT XAE automation, linking, build and target-specific operations.
RuSTy compiler-driver operations exposed through the same gateway.
Language Server Protocol
Starts the compiler-backed LSP surface so protocol clients and higher-level harnesses can consume diagnostics and semantic language operations from the same analysis stack.
Agent tool transport
Exposes schema-described 2ot operations to compatible AI harnesses without maintaining a separate, hand-written command model for agents.
The router can describe itself
Reports the command routes actually installed beside the gateway or available on PATH.
Emits the normalized machine-readable tool surface used for dynamic MCP discovery.
The executable is the source of truth for the installed command surface. A harness can discover that surface programmatically instead of duplicating every leaf executable's evolving help text.
Agent context utility
Packages compiler and semantic context for AI-assisted diagnostic and repair workflows. It complements the normal 2ot router rather than replacing it.