Real terminals, never scraped
Every pane is a byte-opaque PTY. Loom forwards bytes and never reads your screen as a signal — your shell, your agent, your dev server, unmediated.
// agent-first dev environment
Loom is an agentic developer environment. Every pane is a real, byte-opaque terminal — Loom forwards bytes and never scrapes your screen. Coordination runs the other way: your agents drive the whole grid over an explicit control bus, as aloom CLI or loom mcp tools.
macOS · Linux · Windows — free builds on GitHub Releases
// built the other way around
Every pane is a byte-opaque PTY. Loom forwards bytes and never reads your screen as a signal — your shell, your agent, your dev server, unmediated.
A process inside a pane drives every other pane over an explicit inbound bus. It asks for what it needs — Loom never guesses from a screen.
The same ops as a loom CLI and as loom mcp tools — list_panes, send_text, spawn_pane, broadcast. Not bolted on.
Queue cards in the repo, arm the drainer, and Loom keeps dispatching work into fresh panes and refilling slots as each finishes.
Every pane across every workspace at a glance. Tear one off into its own window when a task needs room.
Loom never parses what's on your screen. Your agents push what they're doing and ask for what they need. Every signal is explicit — nothing is inferred from a scrape.
Grab the latest signed build from GitHub Releases — the same artifact that matches a tagged commit. Nothing re-hosted, nothing to trust but the source.