Pre-alpha · shipping Q3 2026

The terminal IDE
for your AI agents.

Run AI agents in parallel — each in its own git worktree. Bring your own API keys. Control the whole thing from your phone. Native to macOS.

BYO API keys Built on cmux macOS · iOS No telemetry
termloop · ~/work/payments-refactor
main
claude-opus · auth-fix
codex · db-migration
gemini · tests
claude · opus-4.6running
fix the OAuth token refresh race condition in src/auth/
→ reading src/auth/oauth.ts, 342 lines
Found the race. Multiple tabs hit /refresh at once; we need a single-flight lock.
→ editing src/auth/oauth.ts (+18 −3)
✓ patched · running test: auth.oauth.refresh
✓ 4 tests passed in 1.2s
codex · gpt-5thinking
generate migration for payments.status → enum
→ scanning prisma/schema.prisma
Current type is varchar. Need a 3-phase migration: add, backfill, swap.
→ creating migrations/20260417_payments_status_enum.sql
⚠ large table (2.1M rows) — using batched backfill
Drafting reversible down-migration...
gemini · 2.5-proidle
cover the new payment flow in e2e tests
Waiting on codex's migration to land before writing fixtures.
→ queued · 3 tasks ahead
paused — will resume when payments-refactor worktree is clean
you · hostwatching
worktrees:
.cmux-worktrees/auth-fix claude
.cmux-worktrees/db-migration codex
.cmux-worktrees/tests gemini (idle)
iPhone connected · 192.168.1.42
Features

Everything an agent-heavy workflow needs.
Nothing it doesn't.

Termloop replaces your terminal. It doesn't bolt an AI panel onto VS Code. Built from the ground up for people who already live in tmux.

Parallel agent sessions

Run four Claudes, a Codex, and a Gemini at once — each in its own pane, each in its own worktree. Nothing collides. Nothing waits its turn.

ClaudeCodexGeminiBYO

Worktrees, first-class

Every task gets its own branch and directory, created automatically. No stashing, no branch gymnastics. Agents can't step on work in progress.

zero-configgit-nativedisposable

Phone in the loop

Start an agent from the couch. Check output from a coffee-shop queue. Native iOS client over an authenticated TCP bridge — no cloud round-trip.

bridgedencryptedasync

Bring your own keys

You pay the model provider directly. No middleman markup, no rate-limit surprises. Termloop never touches your API traffic.

AnthropicOpenAIGoogleOllama

Projects, not just shells

Group workspaces by project, switch contexts in one keystroke. Your "work" project, your "side-project" project — each with its own agents and env.

namespacedpersistentfast-switch

Source-available, auditable

Inspect the socket protocol, the agent loop, everything. No telemetry, no phone-home — what you see on your machine is all there is.

auditableno-telemetrylocal-first
Flow

How a Termloop session runs.

Three steps. No config files. No YAML.

01

Point it at a repo

Open Termloop in any git project. It auto-detects remotes, branches, and dev server scripts.

02

Spawn an agent

Pick a model, give a task. Termloop forks a worktree, boots the agent, and streams output to a new pane.

03

Review & merge

When the agent reports done, review the diff in place. Merge, discard, or hand off to another agent.

Built in the open

Read the source. Trust the loop.

Termloop is built on cmux — a GPL-3.0 terminal multiplexer by Manaflow. We publish our agent layer publicly too. No telemetry, no phone-home. Final license and pricing announced at launch.

Questions

Frequently asked.

Is this a fork of Claude Code / Cursor / Warp?

None of those. Termloop is built on cmux, an open-source terminal multiplexer — think tmux with a native macOS shell. We added a pane-per-agent model, git worktree orchestration, and a mobile bridge. Claude Code and the others run inside Termloop panes, not the other way around.

What models can I run?

Any model with a CLI: Claude Code (Anthropic), Codex (OpenAI), Gemini CLI, Aider, Cline, local Ollama, or your own scripts. Termloop just hands each one a worktree and a pane — it's model-agnostic.

Does Termloop see my API keys or code?

No. Agents call their providers directly from your machine with your own keys. Termloop never proxies, stores, or phones home. The only network call it makes is checking for app updates, which you can disable.

Why macOS-only?

Because we wanted a native, fast, low-latency UI before we wanted broad reach. Linux is on the roadmap. Windows isn't, for now.

How does the phone bridge work?

A native iOS client connects to your Termloop session over a password-authenticated TCP socket on your local network (or over a tailnet if you have one). Same protocol as the desktop — you can list workspaces, switch projects, and watch agent output live.

How much does it cost?

Early access is free. Final pricing will be announced before launch — expect a free tier for personal use and a paid tier for power features like the mobile bridge and cloud session sync. Sign up for early access and we'll tell you first.

What's the license?

Termloop builds on cmux, which is GPL-3.0-or-later with a commercial option by its publisher. The full Termloop licensing terms will be published alongside the first binary. Until then, the repository is source-available for inspection.

Early access

Get the first binary.

One email when Termloop ships. Plus a private TestFlight invite when mobile opens up. No drip.

~ waiting for input