Collection Nº 1 · Autumn – Winter 2026
One person,
many threads.
A coding terminal for multithreaders and ADHD brains.
Wavi — Collection Nº 1

01

04
I · Board
Who’s waiting?
Running, done, stuck: each looks different, in shape and in words. Only the one waiting on you lights up, and ⌘J jumps there.
- (I)
One board for every project.
Needs you, error, to review, running, idle. Each session is a card with its branch, its diff and the checks it ran.
- (II)
Look without leaving.
Press Space on a few cards and up to four live terminals open side by side.
- (III)
Called only when it matters.
The Dock counts who needs you. A notification names the session and what it asked, only when you can’t see it.
05

06 — 07
II · Ensemble
One task,
many hands.
- (I)
Hand it out.
Ask one agent to split the job. It sends the pieces to Codex, Gemini or any of the nineteen, each on a branch of its own.
- (II)
Hear back.
Every piece reports to the session that sent it. You confirm the first hand-off; the rest is theirs.
- (III)
A lead who never codes.
A leader session only hands out work. It takes over sessions you opened, after one yes.
08

09

10 — 11


12
II · Ensemble
Their own
teams, too.
- (I)
Subagents.
Claude Code’s subagents show up under the session that started them.
- (II)
Agent teams.
A Claude Code team gets lanes under its lead: who is on it, who passed what to whom, who is waiting on you.
- (III)
Workflows.
Every phase of a workflow is a row: done out of total, tokens, time.
- (IV)
Same task, several hands.
Give one task to two to four agents, line up the diffs and test runs, keep the best.
13


Still — one mirror, three panels.
14
III · Threads
More screens,
more threads.
- (I)
Split it.
Drag a session into the window: up to four side by side. Split, swap, resize.
- (II)
Tear it off.
Drag one out and it becomes a window of its own, on any screen.
- (III)
Leave it running.
Quit with ⌘Q and reopen tomorrow; agents keep going. Claude and Codex pick up again when your quota resets.
- (IV)
A branch each.
Every agent works in a worktree of its own. Two touching the same code? You hear before you merge.
15

16
IV · Ship
Less git.
More building.
- (I)
Issue in.
Hand an issue or a PR to an agent from the board. It gets a worktree and the task.
- (II)
One button at a time.
Commit, push or open the PR: one lit button. The agent writes the message; you press ⌘↵.
- (III)
Checked before it leaves.
With review before push on, what is about to go up gets reviewed first, and a P1 stops it.
- (IV)
CI fails? Fine.
The agent fixes it and commits; Wavi checks, then pushes. Nothing runs by itself until you switch it on.
17
From issue to main.
- i.
Hand to agent

- ii.
Review before push

- iii.
Create PR

- iv.
CI and auto-fix

- v.
Merge

Plate 09Issue to main. Each step is one button; the agent does the writing, you do the deciding.
18 — 19
V · Wardrobe
Terminal or chat.
Glass or solid.
- (I)
Per session.
Start each session in the terminal or as a chat. Wear both in one window.
- (II)
Your glass.
Liquid Glass or solid, from 20 to 100%. A picture of your own underneath, sharp or blurred.
- (III)
Your type.
One font for Latin, one for CJK. Bring a Ghostty or iTerm theme. Light or dark, English or Chinese.
20
Default · terminal 85%
Your picture · terminal 50%
Blurred · 50%, blur 40%
Appearance settings, light
21