No sign-in required · seeded data

Walk through PairWave end-to-end — in five minutes.

A fully populated workspace. Acme Engineering, six members across four projects, live sessions in flight, a stocked lessons library, and a week's worth of activity ready for you to poke at.

Start at the dashboard Jump into a live session

Demo workspaceacme-eng · team plan

3 teams seeded — personal, Acme Engineering, Tidepool Labs
6 sessions across 8 projects
6 lessons in the library — 1 contested, 1 under-review
4 recent writeups, 2 already promoted
3 paired machines — spawn & control real Claude Code
Per-session token usage + a weekly cost rollup
1 owner audit-log entry — see what notified looks like

Surface 1

Dashboard

Where you land after signing in. Your live sessions, the team's live sessions, this week's stats, and a peek at recent writeups.

Open dashboard →

Your sessions · live & recent6 total

andy/auth-svc·~/work/auth-svc

Your week with Claudeprivate to you

Sessions

Prompts

Writeups

Reports are recipient-private. Sharing scales with the situation, not with rank.

Surface 2

Live session — autoplaying

A real session transcript replaying on a 3.5s cadence so you can see the chat, tool calls, and operator side-channel without signing in.

Open this session →

andy/auth-svc·~/work/auth-svc

Rotate hub signing key without breaking live sockets

visibility: project⊙ 1 approval pendinglive · autoplay

andy/auth-svc·demo · autoplaying

cycle 0

◊

(↪ peer report from @bob/billing) — "60s works for billing. We re-verify on every webhook anyway, and our verifier rebuilds per-request — no cache to invalidate. Suggest you log the active key fingerprint on every verify so we can confirm rotation happened cleanly across services."

ACOperator chat

Good call. The fingerprint log will save us a lot of guessing during the actual rollout.

@andy

Add that fingerprint log to verify(). Then update verify.ts to use the loader.

Editsrc/auth/verify.ts (~28 lines changed)allowed

Bashpnpm test src/authallowed

◊

Full auth suite passes (47/47). Verifier now accepts either current or previous, logs fingerprint at debug level, and falls back to a friendly error if Vault has been unreachable longer than the loader's grace window.

⊙ permission requestedBash

git push origin andy/vault-key-rotation

@andy

We need to rotate the hub's signing key without dropping any open SSE sockets. Walk me through the plan before changing anything.

Hub-mirrored chat

Every Claude turn renders here, with tool calls, verdicts, and approver provenance. Permission cards land inline; click Allow and Claude Code on the operator's machine acts on it.

Operator chat

Side conversations between collaborators that Claude never sees. @-mentions ring a soft chime; one-click 'queue' button promotes a message into the prompt queue.

Cross-session routing

Type @bob/billing in your composer to route a prompt into Bob's session. The reply forwards back as a peer report. Routes to any session you can access; project sessions stay scoped to their members.

Surface 3

Lessons library

Promoted writeups become owned, time-boxed lessons. 90-day review cycle. Stale lessons fall to under-review until refreshed.

Open lessons →

active★ team-wide

Scope rm operations explicitly — never trust 'old' as a filter

When asking Claude to clean up files, always scope by an objective signal (unreferenced in code, last-modified > N days, matched glob). 'Old' is interpreted aggressively.

owned by @alice#bash #safety

active★ team-wide

Front-load the hypothesis, not the trace

Pasting a stack trace alone gives Claude permission to guess. Stating your hypothesis first turns the turn into verification, which is cheaper to be wrong about.

owned by @alice#prompt-craft

active

Backfill in adaptive batches — measure replication lag, back off if >2s

Static batch sizes either underuse capacity or melt replicas. The pattern: start small, observe lag, scale until lag exceeds threshold, back off.

owned by @carol#db #migrations

★ promoted

Front-load the hypothesis, not the trace

Pasting a stack trace alone gives Claude permission to guess. Stating your hypothesis first turns the turn into verification, which is cheaper to be wrong about.

Started life as a writeup (wr_001); promoted because the project agreed it was a durable pattern. Inherits the writeup's pinned moments and adds an owner, a 90-day review-by, and a status.

Surface 4

Teams & projects

Per-project roles (lead / contributor) — not global seniority. Same person can be a lead on one workstream and a contributor on another.

Open Acme Engineering →

Acme Engineering

acme-eng

auth-svc· 4billing· 3data-pipeline· 2General· 6infra-cleanup· 1

6 members · 5 projects · plan: team

Owner audit loglogged & notified

2026-04-29 14:22
@andy (owner) viewed full session
reason: "investigating high spend last week"
2026-04-29 14:23
operator notified: owner viewed your session

Owners get the access they need for governance. Operators retain dignity — they always know when they're being looked at, and why.

Surface 5

Machines

Run real Claude Code on your own workstations. Pair the Relay desktop app once, then spawn and drive sessions from the browser — PairWave brokers a per-machine token and never holds your Anthropic key.

Open machines →

andys-mbp.localonline

daemon v0.4.1

liveandy/auth-svc

idleandy/billing

2 sessions · shared with 2

andy-devboxoffline

daemon v0.4.0

idleandy/embeddings

1 session

alices-studioonlineshared · operator

daemon v0.4.1