Compare
TermFlow vs Wave
We agree on the important thing: never paywall the local terminal or your own AI. Wave is a graphical, block-based workspace. TermFlow is a keyboard-first terminal built for agents across machines.
Two philosophies.
Wave
A graphical, block-based workspace.
Open source, with inline files, previews, and widgets living next to your output. Core plus local bring-your-own-key AI is free forever; cloud and teams are paid. If you like keeping files and results in one visual view, it’s genuinely nice.
TermFlow
A keyboard-first terminal for fleets.
We didn't build a graphical workspace — we built the connective tissue for agents: a full API, an MCP server, headless / API-driven operation, and agents coordinating across machines and platforms, all keyboard-first.
Feature by feature.
| Capability | TermFlow | Wave |
|---|---|---|
| Platforms | Windows · macOS · Linux | Windows · macOS · Linux |
| Open source | ✓ | ✓ |
| Local BYOK AI, free | ✓ | ✓ |
| Graphical block workspace, inline previews | — | Yes ★ |
| Run any external agent CLI | ✓ | ✓ |
| Full REST / WebSocket API | ✓ | — |
| Built-in MCP server | ✓ | — |
| Headless / API-driven operation | ✓ | — |
| Cross-machine agent communication | ✓ | — |
| Remote browser monitoring | Free / local | Cloud, paid |
| Price | Free · paid fleet | Free core · paid cloud/teams |
Where we agree, where we differ
Wave and TermFlow actually agree on the thing that matters most: the local terminal and your own AI keys should never be paywalled. Both are open source and both let you bring your own key. Wave's graphical, block-based workspace — files, previews, and widgets inline — is genuinely pleasant if that's how you like to work. We went the other direction: a keyboard-first terminal whose differentiators are the developer API, the MCP server, headless / API-driven operation, and agents coordinating across machines. Different shape, same respect for developers.
Common questions.
Does TermFlow have Wave's graphical blocks?
No — we're keyboard-first by design. If inline files and previews are central to how you work, Wave is a great fit. If you want agents coordinating across machines with an open API, that's us.
Both are free — so what's paid?
For us: multi-machine and multi-person features. Everything on one machine — API, MCP, headless / API-driven operation — is free. See pricing.
Is TermFlow open source?
Yes, Apache-2.0 — same open posture as Wave.