The coordination layer for coding agents

Closed alpha

Give the mission. The teams form themselves.

Kansei coordinates Claude, Codex, local models, and terminal sessions across your projects. Agents assemble the right teams on demand, spinning up sessions, delegating tasks, coordinating dependencies, reviewing results, and bringing you in only when your judgment is required.

Join the waitlist

Runs locally on macOS, Windows, and Linux · bring your own subscriptions and API keys

Mission-scale
orchestration

From one task to a program spanning projects, give Kansei the goal. Agents determine the path while Kansei keeps every workstream, handoff, review, and dependency moving to completion.

Self-assembling
teams

Agents spin up the right models and specialists, fan out into parallel lanes, confer and peer-review across sessions, then regroup or reshape the teams as the effort evolves.

Command
by exception

See every team in motion, open any session, or take control at any time. Otherwise, Kansei manages waits, recovers stalled work, and brings you in for the decisions that need you.

Illustrative demo

One goal in. A finished PR out.

Give one agent the goal. It spins up the teammates it needs, hands off tasks by name, routes blocking questions to peers, coordinates reviews and dependencies, and brings the results back together. Here's how one mission plays out, turn by turn.

Turn 1done

You→Orchestrator

promptsends

draft the example fix, review it, and open a PR
Turn 2done

Orchestrator→Drafter

gpt-5 · codexassigns

spin up Drafter and Reviewer
Turn 3done

Drafter→Orchestrator

claude-opusreports

refactored the credit-radar filter
Turn 4done

Drafter→Reviewer

claude-opusasks

rename or deprecate the helper?
Turn 5done

Reviewer→Drafter

gpt-5 · codexanswers

deprecate, keep a shim — no human
Turn 6done

Reviewer→Orchestrator

gpt-5 · codexapproves

approved · opened example PR

The bottleneck isn't the model

Your agents got faster. Their handoffs did not.

Running more agents only helps until you become their message bus. Every copied prompt, status check, and stalled question pulls you back into work the agents should be doing together — the walls between providers, projects, and devices are still yours to cross by hand.

Without coordination

More agents. More babysitting.

You shuttle context between windows, ask for status, resolve every question, and notice the quiet stalls. Parallel work becomes a queue with you in the middle.

With Kansei

The team carries the context.

Agents hand off, wait, review, and answer one another through Kansei. You set the mission, inspect any session, and step in only when a decision needs you.

handoffs

Work moves by name, not copy-paste.

zero-request waits

Waiting agents sleep: no tokens spent polling.

durable state

Kansei tracks who is waiting on whom.

control

Open any session. Take command.

Spinning up agents is the easy part — terminals, worktrees, a watch script. Keeping them working as a team takes the hard, invisible engineering: messaging, recovery, visibility, alignment. That layer is Kansei.

The relay, automated

Claude asks. Codex answers. Work keeps moving.

A Claude session can stop on a real implementation choice, receive a Codex peer's answer, and continue — without waiting for you to notice, copy the question, or paste the reply.

DeliveryGate pauses an agent for the replies it declares, using zero model requests while it waits. All gathers the full panel; any delivers available replies individually. Other messages queue until the session is ready, so an answer lands at a safe boundary instead of interrupting the agent mid-thought. The shape follows the work, not a fixed pipeline.

Supervise by exception

Leave the relay. Keep the final say.

World View shows who is working, waiting, blocked, or done. Open any session to redirect it, add context, or take over.

Run the cockpit in your browser, connect through MCP in VS Code or Cursor, or pair your phone with a QR code. Notifications take you directly to the session that needs you; everything else keeps moving while you review, commute, or work elsewhere.

You set the direction and the guardrails. Agents reach out only when they need your call.

Agents · this mission 4 on this mission · 1 needs you

Drafter

claude-code

working

Reviewer

codex

reviewing

Orchestrator

claude-code

idle

Scout

codex

needs you

Illustrative sample mission → open any session, direct, spin up, or close

The payoff

One operator. A whole team's output.

When agents coordinate themselves, you stop being the bottleneck. Dozens of workstreams move at once while your attention stays free for the calls that actually need you — the throughput of a team, running on its own.

Many projects at once

Run a team on every project you own, all advancing in parallel — your output is no longer one thing at a time.

Reclaim your attention

No more babysitting a prompt. The team works while you think, review, sleep, or build something else entirely.

Scale past your own hands

Command an entire team's output on your own. The leverage of many, in the hands of one.

Works with what you already run

Put the agents you already pay for to work together.

Claude, Codex, local models, and terminals share one cockpit and one coordination layer. Keep your existing subscriptions and keys — Kansei turns them into a team without marking up your model usage.

Claude · SDK + PTY Codex and ChatGPT · chat + PTY Local LLM · chat Terminal · PTY VS Code and Cursor · editor + MCP

Yours by design

On your own machine. Private. Secure. Yours.

Leverage shouldn't cost you ownership. Kansei runs on your own machine — your code and your models' responses stay local, with your agents connecting straight to your providers. Privacy and security here are structural, not bolted on.

Your work stays local

Our cloud isn't designed to receive your code or your models' responses — your agents connect straight to your providers.

Never proxied

Bring the subscriptions or API keys you already pay for; inference goes straight to your providers. Kansei isn't designed to receive or proxy your prompts or responses.

Per-device keys you can revoke

Remote access runs through an encrypted tunnel into your machine. Each paired device gets its own key, revocable instantly.

Blind by construction

The coordination layer isn't designed to receive your content. It knows who's working, not what they're working on.

Controlled delivery

Authorized sessions communicate freely. During a wait, only expected replies wake the session; everything else queues. Nothing outside your environment can reach in.

On hardware you control

Your machine, your credentials, your control. The leverage is real, and it's entirely yours.

Read the security architecture →

We're building this in narrow alpha.

Join the waitlist and we'll reach out as seats open up.

Kansei is in narrow alpha. No card, no spam — we'll email you when there's room.

You must be 18 or older. Kansei is not currently offered to persons ordinarily resident in the EEA or the UK.