> ## Documentation Index
> Fetch the complete documentation index at: https://smithers.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up with Pi

> Connect Smithers to Pi with the first-party pi-plugin: a live run inspector inside the Pi TUI. Pi has no MCP client, so the plugin (or skill) is the path.

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.

## Install (recommended)

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:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
bunx smithers-orchestrator init
bunx smithers-orchestrator skills add
```

## 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](/guide/what-you-can-do)) and Pi drives the runs, with the
inspector live in the TUI.

<Note>
  The agent-facing details (extension model, the three integration modes) live
  in the Technical API at [Pi](/agents/pi) and
  [Pi integration](/integrations/pi-integration). You don't need them; Pi does.
</Note>