WAVI

Collection Nº 1 · Autumn – Winter 2026

One person,
many threads.

A coding terminal for multithreaders and ADHD brains.

Download for macOSGitHub

Wavi — Collection Nº 1

Wavi in light mode over a picture of mountains: a sidebar of sessions, one waiting on you, next to a running Claude Code session.
Plate 01Session, light. Your own picture under the glass; only the one waiting on you lights up.

01

Still — one window lit.

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.

  1. (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.

  2. (II)

    Look without leaving.

    Press Space on a few cards and up to four live terminals open side by side.

  3. (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

Wavi’s board in dark mode: session cards in columns for needs you, error, to review, running and idle.
Plate 02Board, dark. Every project by status; the sessions that need you come first.

06 — 07

II · Ensemble

One task,
many hands.

  1. (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.

  2. (II)

    Hear back.

    Every piece reports to the session that sent it. You confirm the first hand-off; the rest is theirs.

  3. (III)

    A lead who never codes.

    A leader session only hands out work. It takes over sessions you opened, after one yes.

08

A leader session in Wavi’s terminal: the sidebar draws the sessions it dispatched as a tree, and a strip under the terminal asks you to start two more.
Plate 03Hand-off, dark. The leader keeps Claude on the form, sends the e2e to Codex and takes over a session you opened.

09

A chat session in Wavi: one agent dispatches three sessions to Codex, Claude Code and Gemini CLI, drawn as a fan of lines, with a report card from Codex underneath.
Plate 04Hand-off, light. One agent splits the job across Codex, Claude Code and Gemini CLI; the reports come back into the chat.

10 — 11

A Claude Code agent team in Wavi: one lane per teammate along a time axis, with arrows for the messages between them.
Plate 05Team, dark. One lane per teammate: coder and reviewer pass the work back and forth; docs waits for you.
A Claude workflow’s run card in Wavi: each phase with done out of total and time, and the agents of the running phase underneath.
Plate 06 — a workflow, phase by phase.

12

II · Ensemble

Their own
teams, too.

  1. (I)

    Subagents.

    Claude Code’s subagents show up under the session that started them.

  2. (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.

  3. (III)

    Workflows.

    Every phase of a workflow is a row: done out of total, tokens, time.

  4. (IV)

    Same task, several hands.

    Give one task to two to four agents, line up the diffs and test runs, keep the best.

13

Wavi in dark mode with two terminal sessions side by side and a file tree on the right.
Plate 07Side by side, dark. Two sessions and the files of one, in a single window.

Still — one mirror, three panels.

14

III · Threads

More screens,
more threads.

  1. (I)

    Split it.

    Drag a session into the window: up to four side by side. Split, swap, resize.

  2. (II)

    Tear it off.

    Drag one out and it becomes a window of its own, on any screen.

  3. (III)

    Leave it running.

    Quit with ⌘Q and reopen tomorrow; agents keep going. Claude and Codex pick up again when your quota resets.

  4. (IV)

    A branch each.

    Every agent works in a worktree of its own. Two touching the same code? You hear before you merge.

15

Wavi’s GitHub board in light mode: open issues and pull requests for two projects.
Plate 08GitHub, light. Issues and pull requests for every project; hand one to an agent in a click.

16

IV · Ship

Less git.
More building.

  1. (I)

    Issue in.

    Hand an issue or a PR to an agent from the board. It gets a worktree and the task.

  2. (II)

    One button at a time.

    Commit, push or open the PR: one lit button. The agent writes the message; you press ⌘↵.

  3. (III)

    Checked before it leaves.

    With review before push on, what is about to go up gets reviewed first, and a P1 stops it.

  4. (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.

  1. i.

    Hand to agent

    Hand to agent
  2. ii.

    Review before push

    Review before push
  3. iii.

    Create PR

    Create PR
  4. iv.

    CI and auto-fix

    CI and auto-fix
  5. v.

    Merge

    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.

  1. (I)

    Per session.

    Start each session in the terminal or as a chat. Wear both in one window.

  2. (II)

    Your glass.

    Liquid Glass or solid, from 20 to 100%. A picture of your own underneath, sharp or blurred.

  3. (III)

    Your type.

    One font for Latin, one for CJK. Bring a Ghostty or iTerm theme. Light or dark, English or Chinese.

20

  1. Default · terminal 85%Default · terminal 85%
  2. Your picture · terminal 50%Your picture · terminal 50%
  3. Blurred · 50%, blur 40%Blurred · 50%, blur 40%
  4. Appearance settings, lightAppearance settings, light
Plate 10Four coats, one session: the default, your picture at 50%, the same picture blurred, and the settings that do it.

21

Download for macOSGitHub

No account · No telemetry · Your agent config stays yours · MIT License

22

23