Integrations

Longhouse reads the session files your CLI tools already produce. No plugins, no provider-side configuration. Bare CLI runs import as unmanaged history; launching through Longhouse creates managed sessions and keeps the control path explicit. Import exists so Longhouse is useful immediately, but starting through Longhouse is the path we want users on.

Seven providers ship today

All seven launch through the native longhouse CLI and land in the same timeline. What they can do after launch differs, and the difference is not cosmetic — it is what each provider's own CLI exposes. The table is generated from schemas/managed_providers.yml, the same contract the runtime reads, so it cannot drift from what the product will let you do.

Search, session detail, and the raw event stream work the same for every row. Those are properties of the archive, not of the control path, so they do not vary by provider.

What gets imported, and from where

The Machine Agent watches each provider's own history directory and imports what it finds there, whether or not Longhouse launched it.

Sessions are deduplicated by provider session ID, so re-importing is safe and idempotent. Anything imported this way is a Shadow session: searchable and observable, with no control path, because Longhouse never owned one.

Notes per provider

Claude Code and Codex CLI are the deepest paths. Both support mid-turn steer, so you can redirect a turn that is already running rather than waiting for it to finish.

longhouse claude
longhouse codex

OpenCode takes send, interrupt, terminate, and pause-answer through its permission reply endpoint. Mid-turn steer lands at the next step boundary: after the running tool call finishes, before the next model call. Pass --model when a session must stay on a specific model; Longhouse carries that choice through the initial launch and a later cold reattach.

longhouse opencode
longhouse opencode --model <provider/model>

Cursor Agent runs as a managed Helm session whose native runtime owns the PTY, control, permission, and transcript lifecycle. Send, interrupt, terminate, mid-turn steer, and reattach work; pause-answer does not.

Pi Agent and Oh My Pi run as managed Helm sessions in the provider's own terminal client. Send, interrupt, terminate, mid-turn steer, reattach, and resume work; pause-answer does not. Each provider keeps its own credentials, which Longhouse does not probe or replace.

longhouse pi
longhouse omp

Antigravity CLI is the narrowest of the seven. It launches under Longhouse's hook-inbox control path and accepts send; interrupt, terminate, and reattach are not supported. It refuses to start if its Longhouse hook is not installed rather than opening an unmanaged session wearing a managed session id, and send stays gated per session on observed hook readiness.

Import an existing machine

The native Machine Agent service is installed with longhouse machine repair --repair-service after longhouse auth. It imports only what the machine's import scope allows (sessions that start from now on unless you chose otherwise; see longhouse machine scope). To backfill history that predates it, widen the scope, or have the Runtime Host run a one-shot import of what the scope allows:

longhouse-server ship

MCP Server

Longhouse includes a built-in MCP server that exposes session search, recall, and coordination to any MCP-compatible host:

longhouse-server mcp-server

This is the same Machine API surface exposed over the MCP protocol. Add it to your Claude Code or Codex MCP configuration to give your agent access to session history.