Termy
Try now

Code and ship
as a team.system.company.

Give your team shared, concurrent agent sessions — without the merge conflicts.

Download
macOS 13+ · Apple silicon · Free in early access
First launch: right-click the app and choose Open
01 — Platform

One workspace.
Every stage of the work.

If you can describe it, Termy can build it — plan, code, test, review and ship, without leaving the editor.

Create a portfolio site

You describe it. Termy builds it.

Say what you want in plain language. The Commander turns it into a task graph and puts agents on it.

Preview

Ship features
without collisions

backend
Run tests

Agents work in parallel.

Each holds an exclusive lease on the code it owns, so two agents can never edit the same thing at once.

Typecheck
Unit tests
Security
Performance
Accessibility
Deploy
Observability

Nothing merges unverified.

Your own build and tests run against every patch. The command, exit code and output are kept as evidence.

02 — Process

From idea
to production.

01

Describe it

Say what you want built. The Commander turns it into requirements, acceptance criteria and a dependency-ordered task graph.

An agent receiving a brief
02

Architect

Contracts first — APIs, schemas, types and events — so every agent downstream builds against the same definition.

Drafting a contract
03

Build in parallel

Specialist agents work simultaneously in isolated worktrees, each holding an exclusive lease on the code it owns.

Parallel workstreams
04

Verify

Your project’s own build and tests run against every patch. The command, exit code and output are kept as evidence.

Finding the bug
05

Review & merge

Only verified work reaches the branch. Protected branches still wait for a human.

Reviewing the patch
06

Ship it.

Deploy to your own cloud as ordinary commits. Observe it, scale it, and let the loop close on production.

Running in production
03 — Engines

Three engines
under the hood.

You never have to think about them. They are what makes the rest of it hold up.

Agent orchestration

Orchestration

A Commander decomposes the goal, assigns specialists and holds them to exclusive leases so their work can never collide.

Model routing

Routing

Every task is priced and matched to a model by capability, latency and remaining budget — with a fallback chain behind it.

Repository intelligence

Retrieval

AST, call graph and history become a task-specific context package. Your repository is never dumped wholesale at a model.

04 — Infrastructure

For building
and beyond.

Termy runs on infrastructure you already trust — so what you build here keeps working long after it ships.

Infrastructure, handled

Hosting, TLS, databases and secrets provisioned for you. Your code and your data stay yours, always.

Global by default

Deploy to the regions your users are in, with latency-aware routing and failover between them.

Secure, as standard

Secret scanning, dependency and container checks, and least-privilege credentials on every agent run.

Works wherever you do

Build and manage projects from the desktop IDE, the web, or your phone — the same workspace throughout.

05 — Capabilities

Powered by the
Termy platform.

Command

Describe it.
Ship it.

Say what you want in plain language. Termy plans it, assigns it and stays out of your way.

Workspace

Build without
the setup.

Database, auth, storage and deploys wired up from the first commit — no scaffolding to babysit.

Any model

Route to the
right model.

Anthropic, OpenAI, Google, Groq or a local endpoint — chosen per task by capability, latency and budget.

Enterprise

Secure as
you scale.

SSO, SAML, SCIM and role-based access, with a full audit trail of every agent action and approval.

06 — Multiplayer

Everyone’s agents run at once,
on your machines, in one session.

No queue and no turns. Each teammate’s agent works in parallel on the same project, in its own worktree, under their own provider account.

Everyone’s agents run at once.

Every teammate’s agent works in parallel on the same project. No queue, no waiting your turn.

Local agents, shared coordination.

Your CLI runs on your machine under your own keys. Only coordination metadata reaches the Brain.

One session, live for all.

Everyone sees the same files, cursors and agent output as it happens.

07 — Coordination

See what everyone’s
agent is about to do.

Overlap is surfaced before the work happens, not discovered at merge time.

 session/token-refresh · your turn
Alex started the main agent
refactor the token refresh in src/auth
hook · UserPromptSubmit — injecting live team state 412 / 700 tokens
COLLISION src/auth/token.ts is held by Rahul
intent: add audit logging · steps 4–7 unclaimed

Coordination context.

Termy compares branches, file paths, planned work and task descriptions, then injects a budgeted summary into the prompt before the agent runs.

 UserService.java · session/token-refresh
1 public String authenticate(…) {
2 Alex jwt.issue(user)
3 Rahul audit.log(user)
4 }
Run this? rev 18
git push origin session/token-refresh
files ✓network ×commit ×push ✓
✓ Approve× Deny first editor wins

Live changes.

Watch teammates’ agents type in the same file in real time, and answer their approval requests. The first valid response wins and is recorded immutably.

 Memory · src/auth/token.ts
Shared memory — 3 pinned to this file
ok
JWT expiry is 15 minutes — do not switch to cookies
src/auth/token.ts · 8a13c2e · Alex
ok
Rate limiter uses Redis; tests use a mock
src/auth/mw.ts · 4f19b7d · Rahul
stale
reserveSlot() writes without comparing — that is the bug
src/net/session_store.ts · 8a13c2e · Priya
git merge origin/main · session_store.ts moved → note flagged

Memory that knows when it’s wrong.

Decisions are pinned to a path and a commit. When the code moves, the note is flagged stale and the next agent is told to re-check it — never silently deleted.

 Sessions · 3 active
Fix the token refresh race
session/token-refresh
⚠ Needs you — Alex’s agent is waiting
claude · Alex2 req
Add idempotency keys
session/payments
● Running — Priya’s turn
codex · Priyaclear

Every session in one place.

Each one shows its owner, branch, agent, files and what it is waiting on. Join as a participant or watch read-only.

08 — Providers

Claude Code and Codex,
in one shared workspace.

Use a CLI already installed on your machine, signed in to your own provider account. Termy never resells or meters tokens.

Claude Code

Termy detects the local CLI, opens its sign-in flow when needed, and installs the coordination adapter.

Codex

Same adapter, same coordination tools. The Brain is provider-agnostic by construction.

Per-user accounts

Every teammate runs under their own account and keys. Nobody’s credentials are ever visible to anyone else.

 Settings · Agents & providers
General
Editor
Agents & providers
Permissions
Sessions
Team
C
Claude Code
Local provider CLI
Connected
O
Codex
Local provider CLI
Connected
Provider: Claude Code
Status: detected on this machine
Tokens: billed to your own account

Bring your own model and keys.

Agents execute locally under your credentials. The Brain coordinates metadata only — your source never passes through it.

Recent highlights

Sep 21, 2026 · Engineering

Ownership leases: how two agents edit one file safely

LTTermy Team · 8 min read
Sep 14, 2026 · Research

Routing a task to the model that should actually do it

LTTermy Team · 6 min read
Aug 30, 2026 · Engineering

Why nothing merges on a model’s word

LTTermy Team · 5 min read
Aug 12, 2026 · Company

Building an IDE that makes you a better engineer

LTTermy Team · 4 min read
View all posts