wavex
macOS · Linux · Windows · MIT
One desktop app for every coding agent you already pay for.
wavex drives the agent CLIs installed on your machine through your own subscriptions. Tabs are sessions, the composer is the input, and the agent works in your real checkout — not a sandbox copy.
wavex does not resell tokens and has no account of its own.
Verify this download
$ shasum -a 256 wavex_0.9.0_aarch64.dmg
sha256
629f2dc21ecf43e4ac1f3eec0e7d159fa74663e2b761fa4ddb25bde27f79a55f
The installer and this checksum both come from GitHub Releases, so it catches a truncated or corrupted download rather than a tampered one. Updates are the signed path: every bundle listed in latest.json carries a signature wavex verifies before it installs anything.
01 — Providers
Eight agents, one window.
Install and sign in to at least one. wavex detects what is on your PATH and offers only that. Switch provider or model per session from the composer — a session started on one agent can be handed to another mid-conversation, and any turn can be sent to a second agent for a second opinion.
then grok login
then fx login
02 — What is in the window
A session list, an editor, a terminal, and git.
Everything the agent touches is in the same window, working on the same checkout you have open in your shell.
Sessions
Every tab is a conversation. Split a tab into panes to run several agents against the same checkout at once, and group tabs by project.
Editor
CodeMirror with a git gutter, inline diffs, lint, and project-wide search. Files the agent touches refresh under you.
Terminal
A real PTY per tab plus a project-wide dock, so a dev server keeps running while you move between sessions.
Git
Stage by file or by hunk, commit, push, pull, switch branches, stash, and open a pull request. Commit messages, PR titles and branch names can be generated by whichever agent is signed in.
Checkpoints
Every turn that edits files is captured, so a bad turn can be undone without touching your own commits.
Inbox
GitHub issues and pull requests across your projects, with comment threads and PR diffs, and one click to hand an item to an agent.
Notes and skills
Scratch notes per project, and the skills your agents expose surfaced in the composer.
Chats
A second mode for the work that is not code, with no checkout, branch, or diff attached. Drag chats into projects, give a project a brief that every chat inside it sends ahead of your message, and pin or archive the rest.
Profiles
Keep separate identities in one wavex install, with their own projects, chats, workspace, and preferences. Your agent CLI sign-ins stay shared across profiles.
03 — How it compares
Your own subscriptions, in a window that knows about git.
Three ways to work with a coding agent. wavex is the middle column: the CLI you already pay for, driven from a window that understands branches, worktrees and diffs.
| Terminal only | wavex | Editor fork with a bundled plan | |
|---|---|---|---|
| Bring your own subscription | Your CLI login, with nothing between you and the provider. | The same login. wavex drives the CLI you installed and resells no tokens. | Its own plan, billed by the editor. Some tiers take your API key instead. |
| Several agents at once | One process per window. You tile them and remember which is which. | Tabs, splits and panes over one checkout. Hand a session to another agent mid-conversation, or send a single turn to a second one for another opinion. | The editor's own agent, plus whatever background runs the vendor offers. |
| Git worktrees |
git worktree add, then a second shell and a second editor window.
|
Created, switched and removed in the window, and a session is bound to the checkout it belongs to. | A second checkout means a second window. |
| Checkpoints | Whatever the CLI keeps, undone by hand. | Every turn that edits files is captured, so a bad turn rolls back without touching your own commits. | The agent panel restores to an earlier point. |
| Remote host | SSH, and a multiplexer to keep it alive. | Drive another machine of your own through a tunnel, or open its window in a browser tab. No relay and no account in between. | Remote SSH, and the cloud agents the vendor runs. |
| No lock-in | There is nothing to leave. | MIT, and the CLIs stay yours. Uninstall wavex and every agent still works in your terminal exactly as before. | A proprietary editor, and the agent history lives inside it. |
The third column describes a category — editors such as Cursor and Windsurf — rather than any one product, and those feature sets move quickly. Check the current version before you take this as a scorecard.
04 — Questions
Before you download.
Do I need an account?
No. wavex has no sign-up, no account and no backend of its own. You sign in to the agent CLIs you installed, exactly as you do in a terminal, and those credentials stay with the CLI — wavex never sees them.
What does it cost?
wavex is free and MIT-licensed. What you pay for are the CLI subscriptions or API keys you already hold. wavex drives them; it resells no tokens and adds no margin.
Does my code leave the machine?
Not through wavex. It is local-first: sessions, notes and settings are files on your disk, and there is no server to send them to.
It is not airtight on its own, though, and the honest version matters here. The
agent CLI you installed sends the prompts and files you give it to its own provider,
exactly as it does in your terminal. wavex's own calls all go to GitHub: the update
check reads latest.json, and the Inbox reads the issues and pull
requests your GitHub account can already see. Nothing else is contacted.
Is there telemetry?
None. No analytics SDK, no crash reporter, no usage ping — there is nothing in the app that reports back, and no switch to turn off. The Usage view reads the summaries your provider CLI already wrote on your machine.
What happens to my checkout?
The agent works in your real repository, not a sandbox copy, so wavex treats it as your data. Every file-editing turn is checkpointed, uncommitted work is preserved rather than reset, and an agent can be put on its own git worktree to keep your branch clear.
Which platforms?
macOS on Apple Silicon, Linux on x86-64 and Windows on x86-64. Every release builds all three. There is no Intel Mac build.
05 — Install
Every file in this release.
Version 0.9.0, straight from GitHub Releases. The updater feed for the same build is latest.json.
629f2dc21ecf43e4ac1f3eec0e7d159fa74663e2b761fa4ddb25bde27f79a55f
dd504d589f0310c0bd5de34acaef33826e3f2f91786d58385250682e6bdc6056
ce64f3e9a35a9e715d5594b0af77fa49781baa42183f206f087e350ec64d55fc
32e181e8cc7ee322711a54bd6a6535b1ff5f4bdff2b30dce6bf5c888da070203
137f512264869b458e289abc11f89947c50485c554f2878ffe156b8cacbf4e46
macOS, Linux and Windows.
Pick the file for your machine, then sign in to at least one agent CLI.
- macOS (Apple Silicon) — open the .dmg and drag wavex to Applications. The build is signed with a Developer ID certificate, notarized by Apple, and stapled, so it opens without a Gatekeeper prompt.
- Linux (x86-64) — take the .AppImage and mark it executable, or install the .deb or .rpm. wavex needs WebKitGTK 4.1, which every current desktop distribution ships.
- Windows (x86-64) — run the -setup.exe installer. It installs for the current user, so it needs no administrator rights.
The Windows and Linux builds are not code-signed yet, so SmartScreen may warn on the first run. Update bundles are signed on every platform and wavex verifies that signature before it installs one.
Or build from source.
Node.js 22+, pnpm, and a current stable Rust toolchain — plus the Xcode Command Line Tools on macOS, the WebKitGTK development packages on Linux, or the MSVC build tools and WebView2 on Windows.
$ pnpm install $ pnpm tauri dev
Small, focused pull requests are welcome. Security reports go through private advisories, never a public issue.