The coding agent that asks before it acts.

A calm terminal desk. Plan when you think, Build when you’re ready.

pip install pairwit && pairwit

Read the guide

Files · Editor · Schedule Pairwit — kimi-k2.6 · moonshot · Build 17:32:04

YouCopy

Fix the flaky auth test and write the patch.

PairwitCopy

I’ll edit tests/test_auth.py. Waiting for your OK.

Approval · write_file

tests/test_auth.py

Allow this write?

Once Session Always Deny

write_file · Session · applied

+ def test_auth_retries_once():
+     assert client.login(user).ok
- def test_auth_flaky():
-     assert client.login(user)

> Ask Pairwit anything… (Ctrl+O to attach)

How it works

Install, chat, open the desk, then approve a write — see the product before the pitch.

Files · Editor · Schedule Pairwit — kimi-k2.6 · moonshot 17:30:03

$ pip install pairwit && pairwit

Successfully installed pairwit

Launching desk…

The coding agent is online.

Consent-first · local TUI

> Ask Pairwit anything… (Ctrl+O to attach)

From your project root: pip install pairwit && pairwit

Files · Editor · Schedule Pairwit — kimi-k2.6 · moonshot 17:31:19

YouCopy

who are you?

PairwitCopy

I’m Pairwit — a consent-first coding agent in your terminal. I can read and edit files, run shell commands, and search the project.

Tab Plan (analyze) · Build (apply)
Mutators ask: Once · Session · Always · Deny

↑ 1,750 sent · ↓ 90 received · 3.8s · $0.0020

> Ask Pairwit anything… (Ctrl+O to attach)

Transcript cards and a prompt bar. @ mentions a file · Tab Plan/Build · mutators still ask in Build.

Files · Editor · Schedule Pairwit — kimi-k2.6 · moonshot 17:30:03

torso/

├─ docs/

├─ pairwit/

│ └─ types.py

└─ site/

pairwit/ai/types.py

1
2
3
4
5
6

@dataclass(frozen=True)
class ModelInfo:
    id: str
    provider: str
    label: str
    vision: bool = False

The coding agent is online.

> Ask…

Files and Editor beside chat. Drag ┊ to resize; double-click to reset.

Files · Editor · Schedule Pairwit — kimi-k2.6 · moonshot · Build 17:32:04

Approval · write_file

pairwit/tui/app.py

Allow this write?

Try a choice — keys 1 2 3 n work in-app.

Writes and bash pause for Once / Session / Always. Rules live in .pairwit.permissions.

User guide — panes, schedule, approvals, shortcuts →

Shipping now

Queue work for later

Pairwit runs it while your terminal’s open — no daemon, no cron. Press /schedule when you’re ready.

/schedule or header Schedule
n new · e edit · r run now · p pause
Honors Plan / Build and your approval rules

Schedule in the user guide →

Files · Editor · Schedule Pairwit — kimi-k2.6 · moonshot 17:34:12

Runs while Pairwit stays open.

> /schedule

What you get

Files, editor, Plan/Build, and /schedule — consent-first by default.

Files and editor beside chat

Open the tree, edit buffers with syntax highlighting, save without leaving the agent. Chat stays the main column.

Files · Editor Pairwit — kimi-k2.6 · moonshot 17:30:03

torso/

├─ pairwit/

│ └─ types.py

└─ site/

pairwit/ai/types.py

1
2
3
4
5

@dataclass(frozen=True)
class ProviderSpec:
    id: str
    label: str
    protocol: str

Approvals that stick

Once, Session, Always, or Deny — then remember Always in .pairwit.permissions so the same write doesn’t ask again.

What Pairwit is — and isn’t

Consent-first coding agent (local Textual TUI)
Plan / Build, approvals, sessions, /schedule
Multi-provider (Moonshot, OpenAI, Anthropic, Ollama, …)

Not a full IDE or cloud watcher
Not silent about side effects

Files · Editor · Schedule Pairwit — kimi-k2.6 · moonshot 17:35:01

> /provider

▸ Moonshot default

OpenAI · Anthropic

OpenRouter · DeepSeek · Ollama

Pick a provider · /model to switch

> /provider

The coding agent that asks before it acts.

Local TUI. Your keys. MIT.

pip install pairwit && pairwit

User guide →