LonghouseLonghouse/Docs
GitHubDiscord

Longhouse Documentation

Mission control for CLI agent sessions running on machines you own. Import the history you choose, then start new work through Longhouse so it stays steerable for later.

New here? Start with the Quick Start — you will have Longhouse running, your first session in the timeline, and the normal launch path in under two minutes.

What Longhouse Does

Longhouse puts Claude Code, Codex CLI, Cursor Agent, OpenCode, Pi Agent, Oh My Pi, and Antigravity CLI sessions into one searchable timeline. Bare provider runs land as unmanaged history. When you launch a session through Longhouse, it becomes managed, so you can send to it, tail it, or continue it later from the browser, CLI, or API.

Managed vs unmanaged. Imported sessions are useful immediately for search and inspection, but they are not the long-term happy path. Only managed sessions keep a live control path.

The core loop

  1. Import — Longhouse reads the session files your CLI tools already produce: new sessions by default, older history when you choose it. No workflow changes required.
  2. Find — Full-text search across every conversation, tool call, and file edit. Find the session where you already solved the problem.
  3. Inspect — Open the raw transcript and event history. The model already did the work; Longhouse makes it reusable.
  4. Control — When you launch through Longhouse, the session becomes managed and stays reachable. Send it a message, tail its events, or continue where it left off.

How It Runs

The Runtime Host is a FastAPI server backed by SQLite, and a Rust Machine Agent runs on each machine where you work. Your data stays on your machines. There are no external services to configure for the self-hosted path.

It works on your laptop for quick lookups. It shines on a machine that stays on — a VPS, Mac mini, or homelab box — where sessions keep running after you close the lid.

Guides