v0.6.0  macOS Apple Silicon via GitHub Releases  ·  build from source →
Never blocked by one AI vendor  |  Tauri + Plain TS + Rust

A continuation workspace for AI coding agents.

One calm, chat-first app that drives the coding CLIs you already have installed, keeps each conversation resumable in its native session, and lets you move work to another agent without losing context.

⚡ You pay Anthropic, OpenAI and GitHub. Fullhouse makes sure you never sit idle when one says 'limit reached'.
✓ Local-first: no accounts✓ Zero telemetry✓ Your own CLI credentials
fullhouse / ojspace-engine git:(main) clean
● daemon: ready v0.6.0
Workspaces
● ojspace-engine
○ infra-broker
○ client-telemetry
Active conversations
Zero-copy RingBuffer
Claude Code · sess_89fb · running
Postgres MCP Query
limit → handoff ready to Codex
You10:42:19
Refactor ipc-channel.ts to use Bun FFI zero-copy ringbuffer for low-latency streaming events.
● Codex CLI (resumed from Claude handoff)Turn 4
Inherited worktree .worktrees/refactor-canvas-ipc. Inspecting memory fence invariants:
+ const ring = getOrAcquireRing("/var/run/fullhouse.sock");
+ const fence = createMemoryFence(Release);
return { dispatched, status: 'SYNCHRONIZED' };
Message agent, type / for commands, @ to mention files…
Esc stops · Shift+Tab plan · ↑/↓ recallsess_c81a94f
Handoff ledger ✓ signed
SOURCE → TARGET
Claude Code → Codex CLI
Reason: limit reached
SANITIZATION
ANTHROPIC_API_KEYredacted
worktreepreserved
Works with the coding CLIs you already have installed
CC
Claude CodeNative CLI
CX
Codex CLINative CLI
GH
CopilotNative CLI
OC
OpenCodeNative CLI
AG
AntigravityNative CLI
KC
Kilo CodeNative CLI

+ 20 more via ACP: Gemini · Qwen · Cline · Cursor · goose · Amp · Kimi · Grok · Trae · Hermes  |  fail-closed permissions

The architecture

Work survives the switch.

Fullhouse is where your multi-agent work survives rate limits, crashes, and vendor lock-in.

01 / EXACT RESUME

Exact resume — not “latest”.

Tracks the exact native session ID (--resume, exec resume, -s). Never guesses which conversation was yours.

→ 1 file per chat under app-data chats/
02 / SAFE SWITCH

Reviewed, redacted handoffs.

Rust core parses transcripts, masks credentials, shows what moves, and links the target chat to the project root.

→ Signed ledger + atomic 0600 manifests
03 / CONTINUITY

Continue on limit banner.

When a provider rate-limits, one click continues in your fallback agent with the same git worktree. No copy-paste.

→ Target inherits source worktree
Developers

Install Fullhouse v0.6.0

Tauri + plain TypeScript + Rust core. Clone, run, and drive the agents you already pay for.

# 1. Clone & install
git clone https://github.com/ojspace/fullhouse-cli.git && cd fullhouse-cli && bun install
# 2. Launch desktop app
bun run desktop:dev
# 3. Optional: global CLI
cargo install --path .
GitHub Releases →Source · MIT
Q & A

Frequently asked

Short answers, no marketing fog.

Do I need new API keys?

No. Fullhouse drives CLIs you already authenticated (Claude Code, Codex, Copilot). It never asks for or stores provider keys.

What happens on “limit reached”?

A banner offers one-click “Continue in <agent>”. Transcript is extracted, secrets redacted, worktree preserved, fallback agent started.

Where are chats stored?

One JSON file per chat under the OS app-data path — inspectable, greppable, backed-up. Not browser localStorage.