Super-fast compiler feedback for the harness you choose
Automation scripts and LLM harnesses can use the compiler-only path for rapid compile and diagnostic feedback, while engineers stay in the workflow they prefer and review structured results there.
Runs compiler analysis without starting vendor software, avoiding the startup and project-loading cost of a full vendor check.
Automation can correlate fast compiler findings with their vendor counterparts before an authoritative vendor build is requested.
Harnesses receive stable machine-readable diagnostics with semantic and source context for explanation and repair.
The fast compile loop
The performance story is the compiler-only path. 2ot check --fast stays inside the 2ot compiler and returns compile-time diagnostics without paying the cost of launching or driving a vendor IDE. It is designed to sit underneath automation loops: a script, CI job or LLM harness can request diagnostics, consume the structured result and decide the next step.
The engineer chooses the interface
2ot does not require an engineer to adopt a particular front end. The harness can be an internal engineering tool, a vendor-side integration, an automation script, CI or an agent runtime. The engineer controls that workflow; 2ot provides the execution and structured diagnostic layer underneath it. Direct CLI use remains available for setup, inspection and debugging.
Vendor diagnostics remain the reference
Fast compiler feedback remains useful because automation can relate a 2ot finding to what Siemens TIA, CODESYS or TwinCAT reports. 2ot keeps a one-to-one diagnostic mapping with the vendor diagnostic model where a matching vendor diagnostic exists, while preserving the original 2ot code and structured metadata for the calling harness.
Enrichment for repair workflows
2ot can attach context around a diagnostic instead of returning a bare error string. The result is a better input for LLM-assisted diagnosis: a stable code, structured location and semantic context that can be connected back to the source and the relevant language rule.
Authoritative build when it matters
Vendor software remains the final authority for a vendor build. A harness can use the fast path during iteration, then route an authoritative build through the configured vendor runtime when the exact target toolchain result is required.