Termic vs Xirp
Spotify opened Xirp to public beta in August 2026. Same shape as Termic: run the real agent CLIs in parallel, one git worktree per session, watch them from one window.
The products diverge on who they are for. Xirp is the way into Portal, Spotify's Backstage platform, and it is where the organizational context comes from. Termic is a local app with no account, no backend and a cage you can put around each agent.
01
Xirp is the front of a platform
The app is free. Portal, which supplies the catalog and ownership context every launch post points at, is a per-developer annual subscription. That is the business.
02
Termic is one local app
No sign-in, no daemon to keep healthy, no organization record for your repo. It opens a folder and spawns the CLI you already installed.
03
Only one of them cages the agent
Termic can lock a task to its worktree with macOS Seatbelt and a network allowlist. Xirp adds no isolation of its own.
feature by feature
What changes in practice
Short version: Xirp wins on organizational context, session polish and agent-driven fan-out. Termic wins on license, account, size, platforms, agent count, multi-repo work and the sandbox.
Best fit
License
Price
Account required
Platforms
Runtime and size
.dmg. .dmg for version 0.12.0. Runs the real CLI
Agents supported
claude, codex, gemini, Antigravity, opencode, Copilot and Grok. Any PTY command can be registered in about 30 seconds. Git worktrees
Work on the main checkout
Multi-repo work
Sandbox around the agent
Work-done detection
OSC 9;4, window titles). No config, works for agents added by hand. Organizational context
Session transcripts
Agent-driven orchestration
Context-window meter
Auto-named sessions
Grid of live terminals
Background processes
Last reviewed: 2026-08-11, against Xirp 0.12.0. Claims come from the public sources linked below and from running the app. If something changed, file an issue.
pick xirp
Use Xirp when the catalog is the point
The context argument is a good one and Termic has no answer to it. Most bad agent output is not bad code. It is correct code written by something that had no idea what system it was sitting inside. Starting a session with ownership and dependency data loaded is a real fix for that.
If your company already runs Backstage or Portal, that data exists and Xirp is built to hand it to the agent. Nothing local competes with that.
Two things to know going in. The context lives in Portal, which is a per-developer annual subscription, and a catalog that has drifted will hand agents confident nonsense they cannot detect.
pick termic
Use Termic when it is your machine and your repo
No account to create before you can open a folder. No organization record for a side project. No daemon. 20 MB of native app instead of 183 MB of Electron, which starts to matter when a dozen live terminals are painting at once.
Seven agents built in and any PTY command can become the eighth, so the tool does not decide which vendors you are allowed to try. macOS and Linux. AGPL source you can read, fork or audit.
And a real boundary. Each task can be locked to its worktree with macOS Seatbelt and a network
allowlist, pinned at creation. Termic caught Claude Code reaching for
~/.config/gh/hosts.yml and browser profile directories while idle. Inside
the cage that read fails. Outside it, it quietly succeeds.
knowing when an agent is done
Hooks versus the terminal
This is the most interesting technical difference and it is invisible until you run twenty sessions.
Xirp writes hooks into your agent's configuration, for Claude and Codex. That is precise where it is installed. Its onboarding is also blunt about the cost: without hooks, status badges and notifications do not work.
Termic reads what the agents already send the terminal. Claude Code emits
OSC 9;4 progress states, Gemini and Codex put the state in the window
title. It is why iTerm shows a spinner. No config, no file written to your home directory, and it
works for an agent added by hand five minutes ago.
It also survives the cases a completion event misses. Interrupt a turn and nothing completion-shaped fires, because the turn did not end, it was cancelled. The terminal signal still flips.
questions
Comparison FAQ
Is Termic an open source alternative to Xirp?
claude, codex and gemini binaries in parallel, each session in its own git worktree. Termic is AGPL-3.0 with a public repo, needs no account, and ships a per-task sandbox. Xirp is closed, macOS only, and asks for a Spotify login before you open a repo.Is Xirp free?
When should I pick Xirp?
When should I pick Termic?
Do both run the real CLIs?
Does Xirp have a sandbox?
How does each one know an agent has finished?
Does my code leave the machine?
Can I use both?
sources
What I checked
Xirp's public site, docs and launch post, reviewed on 2026-08-11. The size and version numbers come from their published release manifest. The rest comes from installing Xirp 0.12.0 on a Mac and using it. No vibes.
Install Termic
Free. AGPL-3.0. macOS and Linux releases now.