2ot check --fastcompilerFast diagnostics
Run compiler diagnostics without starting a vendor IDE where supported.
This overview covers source-backed gateway families, not every installed subcommand. Use 2ot help, 2ot --list --json and 2ot --mcp-dump-schema for exact flags and channel-specific exposure.
2ot check --fastcompilerRun compiler diagnostics without starting a vendor IDE where supported.
2ot test prepareutilityPrepare test inputs through a reviewed CLI-only route.
2ot transpile ...compilerEnter compiler conversion routes; use installed help for exact flags.
2ot build ...workspaceTarget-bound build. Consequential routes require transaction authorization.
2ot lspprotocolProvide compiler-backed language intelligence to compatible clients.
2ot mcpprotocolExpose reviewed MCP-eligible operations; raw persistent mutation is denied.
2ot probes ...utilityAccess supported probes; inspect local help and policy first.
2ot run ...utilityDispatch reviewed run routes subject to operation and effect policy.
2ot tests ...utilityAccess installed test routes where supported.
2ot capabilities <tia|twincat|codesys>discoveryReport CLI-only registry metadata without live vendor probing.
2ot rusty ...vendorReach registered RuSTy compiler routes.
2ot tia ...vendorReach reviewed Siemens operations on a suitably licensed host.
2ot codesys ...vendorReach registered CODESYS operations where supported.
2ot twincat ...vendorReach registered TwinCAT operations where supported.
2ot tx ...workspacePlan, review, authorize, execute and retrieve receipts through the protected service.
2ot --list --jsondiscoveryEnumerate local CLI commands; MCP exposure may differ.
2ot --mcp-dump-schemadiscoveryDescribe reviewed MCP-eligible tools on this installation.
2ot help <command> [subcommand]discoveryInspect installed subcommands and arguments rather than guessing ellipses.
Website discovery is informational. CLI and MCP share reviewed contract definitions but do not expose identical sets: some commands are CLI-only. The installed executable and its policy remain authoritative.
These are the protected 2ot tx exit meanings documented by the transaction service, not a claim that every vendor child uses the same codes. JSON transaction responses expose fields including schema_version, status, code, operation_id and recommended_action.