Install & Setup
Choose a Statewright integration for your coding harness or MCP host
Install & Setup
Use your workflows in the harness you already work in. Choose an integration below; installation, authentication, tool enforcement, and model routing depend on the host.
| Harness | Setup guide |
|---|---|
| Claude Code | Native plugin and OAuth |
| Codex | Plugin and browser approval |
| Cursor | Executor hooks or advisory IDE mode |
| OpenCode | Native plugin through the executor |
| Pi | Extension and optional executor setup |
| Oh My Codex (OMX) | Native hooks and executor setup |
| Claude Desktop | Code → Local |
| ChatGPT Desktop with Codex | macOS launcher |
| Other MCP hosts | Connection boundaries |
Claude Code
Use Claude Code engine 2.1.295 or newer. Start claude, then run these commands at its prompt:
/plugin marketplace add statewright/statewright
/plugin install statewright@statewrightOpen the Arbiter's connection status and choose Connect. Complete the native permission prompt and Statewright sign-in; Claude owns the saved OAuth login. No API key file or special launcher is needed. See the Claude guide.
If upgrading an installation made with setup.sh or manually added settings
hooks, complete the legacy-hook migration
before starting a workflow. A plugin update alone cannot remove those hooks.
Codex
In your terminal:
codex plugin marketplace add statewright/statewright
codex plugin add statewright@statewrightRestart Codex, then ask it to call statewright_connect. Confirm the matching device code in the browser, select a sign-in provider, and approve. Codex waits for the result and stores the credential in your operating system's credential store. You do not need to generate or paste an API key first.
Continue with the Codex guide or OAuth login guide.
Cursor, OpenCode, Pi, and OMX
Follow the guide for your host in the table above. The shared executor connects these adapters to Statewright and manages workflow sessions. Authentication instructions are specific to each adapter; the Claude and Codex browser flows do not apply to every host.
Cursor's standalone MCP/rules mode is advisory. Its executor mode adds native tool hooks. OMX applies model routes at startup; it does not provide the same live routing boundary as Pi or OpenCode. Use the host guide to check which controls apply to your setup.
Desktop
- Claude Desktop: the same native plugin in Code → Local. Send the first message to start the session and display the Arbiter.
- ChatGPT Desktop with Codex: use the macOS ChatGPT + Statewright launcher for local Codex-backed conversations.
These integrations do not attach local tools to an ordinary cloud chat.
Other MCP hosts
An MCP-capable host can connect to a Statewright gateway to list and load workflows, read the current phase, and request transitions. Configure the gateway and authentication through your host's connection settings; see the MCP tool reference and self-hosted guide.
A remote MCP connection does not give Statewright control over every native host tool or its model selection. Those controls require an adapter that can intercept tools or apply model settings. Native host permissions still apply.
Verify the connection
Ask your host to list Statewright workflows. A newly created account should have a starter workflow. Then follow the Quick Start. If Codex's browser approval does not return to the session, see OAuth login troubleshooting.