src/routes/+page.svelte +42 -3self-hosted · end-to-end encrypted
Run agents in parallel on machines you control, your laptop or a remote box over SSH, and watch and steer every session from your desk or your phone.
A relay you host yourself, cryptographically unable to read your prompts, your code, or your files.
src/routes/+page.svelte +42 -3Why it exists
Existing agent tools force a trade. You get remote parallelism but no phone. Or a mobile relay but no worktree orchestration. Or bring-your-own-key voice, but self-hosting quietly drops the encryption. loombox is the combination that does not make you choose.
emdash
Great SSH, multi-worktree orchestration. No mobile, no sync, no encryption.
Happy
Self-hostable relay + real E2E mobile. No worktree parallelism, voice locked behind a paywall.
HAPI
Bring-your-own-key voice, multi-provider. No SSH; self-hosting drops E2E.
Nimbalyst
Clean server-blind wire protocol. No remote nodes, server closed source.
loombox is the one combination: agents run where you want, you steer from your phone, and you own the relay, structurally unable to read your data.
How it works
loombox weaves many parallel agent sessions into one shipped product, and keeps the whole thing on infrastructure you control.
Spin up parallel sessions on your laptop or a remote box over ssh:, each in
its own isolated worktree. Same-folder safety and a cross-node ownership lease keep two
sessions from ever colliding.
Watch live output, approve tool calls, drop into an interactive terminal, and reply to a session from a desktop browser or an installable phone PWA. An attention inbox and push tell you the moment an agent needs you.
Ship one Docker image, run your own Postgres-backed relay. It routes only opaque ciphertext and routing metadata, never your prompts, code, or files. See how.
Works with ACP coding agents, Claude Code today, Codex and Gemini reserved. Device pairing and recovery codes are yours. Voice, when it lands, runs on keys you hold, not a maintainer's account.
Blind by design
the relay sees who talks to whom, and moves opaque bytes between them. nothing else.
Every payload is sealed on your device and opened only on another device you own. The relay's Postgres holds routing metadata and opaque ciphertext, so a full database dump reveals nothing about your work.
Self-host
loombox ships as a Docker image and a compose file. Bring a box, bring a domain, and you have your own cockpit in a few minutes, with automatic TLS in front and your data on your disk. No account with anyone, no tenant you share, no vendor who can read your history.
# one image, your box, your domain docker compose up -d relay # Caddy fronts it with automatic TLS relay.loombox.dev { reverse_proxy 127.0.0.1:5185 } # the relay stores ciphertext only curl https://relay.loombox.dev/health # -> {"status":"ok"}
Free, open source, and yours to host. Built single-tenant, for one self-hosting developer, first.