Ashigo · Rung

The AI agent for OT engineers.

Diagnose PLCs, historians, and industrial networks in plain language — straight from the terminal. Tools run locally and read-only by default; sensitive data never has to leave the plant.

Install with one command

$ curl -fsSL https://ashigo.com/install.sh | sh

Detects your OS and CPU, drops a single static binary on your PATH — no Python, no runtime. Then run rung.

Windows (PowerShell)

PS> irm https://ashigo.com/install.ps1 | iex

Prefer a file? Download the Windows binary (.exe) and run it directly — no install needed.

Capabilities

It speaks OT, not just English.

Every tool runs on the engineer's machine, with approval prompts and a read-only posture toward live control systems.

Industrial protocols

Modbus reads, OPC UA browse & read, and historian SQL (SELECT-only) — connect to live equipment safely, without leaving the terminal.

Network diagnostics

Ping, traceroute, DNS, and TCP port checks to map segmentation, find comms drops, and validate paths across OT networks.

Log & file analysis

Parse SMC, ArchestrA, and Windows logs by severity; read, grep, and edit local files and exports with diff previews and approval.

Shell, on your terms

Run commands with per-action approval — allow once, always, or deny. Nothing executes on a control system without you saying yes.

OT knowledge & playbooks

Grounded in Aveva, historians, and Rockwell / Siemens / Schneider know-how — and structured troubleshooting it can walk you through.

One binary, anywhere

Self-contained for Windows, Linux, and ARM gateways. No runtime, works offline, and never holds an AI provider key.

Privacy levels

Choose how much leaves the plant.

Hover a level to see what it does — and watch the data flow adapt below.

Standard

Fastest

    INTERNET OT NETWORK Answer page operator reads Reasoning modelorchestrator Data distillerregion-routed Ashigo backendproxy · metering On-site relayIT gating OT terminaltools run here PLC Historian
    How it works

    Reasoning in the cloud. Action and data control on-site.

    The agent loop runs on our backend; the tools run on your machine. The backend brokers and meters every model call, so the CLI never holds an AI provider key.

    • Tools execute locally, with your approval.
    • An optional on-site relay lets IT gate every capability.
    • Privacy levels keep raw data out of any single vendor's hands.
    rung — session
    rung ❯ is PLC 10.0.4.21 reachable, and what's on holding register 40001?
    ✻ Thought for 2.4s
    ╭─ ⚙ ping · 10.0.4.21
    4 packets · 0% loss · avg 1.8ms
    ╭─ ⚙ modbus_read
    │ host=10.0.4.21 table=holding_registers address=0 count=1
    Allow? [y] allow once · [a] always · [n] deny
    holding_registers @ 0 (unit 1): [ 1472 ]
     
    The PLC is online (0% loss). Register 40001 reads 1472
    here's what that maps to and what to check next…
    Get started

    Up and running in three steps.

    Install

    Run the one-line installer above, or drop the binary onto an air-gapped terminal by hand.

    Sign in

    Run rung and /login. The terminal never sees an AI provider key — your account brokers every call.

    Ask

    Describe the problem in plain language. Approve tools as they run, or set a privacy level with /privacy for sensitive sites.