Skip to main content
Pi has a first-party Smithers plugin, so the plugin is the way we recommend. It goes deeper than any other harness integration: tools to launch, approve, and cancel runs, plus a live run inspector (run tree, frame scrubber, node inspector) inside the Pi TUI. Pi deliberately has no MCP client, so MCP is not an option here. Ask Pi:
“Install the Smithers pi-plugin (@smithers-orchestrator/pi-plugin) and set up Smithers in this repo with bunx smithers-orchestrator init.”
Prefer just the skill without the inspector? Run:

​
Check it worked

Say:
“What Smithers workflows are available here?”
Pi should list them via the plugin’s tools. From there, ask for outcomes (What You Can Do) and Pi drives the runs, with the inspector live in the TUI.
The agent-facing details (extension model, the three integration modes) live in the Technical API at Pi and Pi integration. You don’t need them; Pi does.