For builders who want the newest tools first

Don't let a screen decide
how many agents you run.
Put them on a board.

An infinite board of real terminals running Claude Code, Codex, Gemini and 30 more. Everything on your Mac, on your own subscriptions.

hypervibe · full tour 52s · loop

RUNS CLAUDE CODE · CODEX · GEMINI CLI · GROK · OPENCODE · AND 30 MORE

01Board

Real terminals on an infinite board.

Ctrl-C works. Vim works. htop works. Every console is the real CLI in a real PTY, exactly like your terminal app. Terminal tabs hide what is running; a board keeps every agent where you left it. Pan and zoom across as many as you need, in workspaces you switch like tabs.

board · 21 agents 20s · loop
web · localhost9s · loop

Live web tiles

Tabs with a live localhost preview, plus a real Web Inspector docked to the board.

kanban · notes · calendar65s · loop

Kanban and notes

Plan next to the work: kanban, sticky notes, text and checklists beside your consoles.

ink · markup11s · loop

Ink and markup

Draw directly on the board and mark up dropped images in place.

git · push8s · loop

Git, on the board

A live card of your branches and a GitHub panel for commit, push and pull.

02Voice

Talk to the whole board.

Hold to talk and say it: pause codex, spawn three claudes, loop the tests. The planner reads plain speech in your language and lands each command as a prepared prompt. The Enter is yours. Audio is transcribed on your Mac and never leaves it.

media/voice.mp4 video · 16:10 · con audio opcional
placeholder

Voice orchestration, end to end

Grabar: mantener push-to-talk y decir "spawn three claudes": mostrar el command center armando el plan, las tres consolas apareciendo y los prompts preparados esperando tu Enter. Incluir una @-mencion a una consola concreta y cerrar con un "pause codex".

03Orchestration

Who is working, who is resting, who needs you.

Somewhere in your tabs, an agent is waiting for you. On the board you can see it: the mission map shows every console as working, resting or needing you, with status driven by the CLI's own hooks. Group consoles into teams with roles. Hand a task from one agent to another with its state: the outgoing session is summarized and the brief lands on the new agent.

media/teams.mp4 video · 16:10 · autoplay loop
placeholder

Teams and the mission map

Grabar: armar un equipo de 3 con roles, pedir un team report, hacer un handoff de claude a codex ("pasale esta tarea a codex") y abrir el mission map con los estados cambiando en vivo.

media/loops.mp44:3
placeholder

Grabar: crear un loop con schedule y goal, verlo disparar una vez y retirarse al cumplir el goal.

Loops that know when to stop

Trigger a console on a schedule, on idle or on output. Give the loop a goal and it retires itself once the goal is met.

media/composer.png4:3
placeholder

Captura: el composer con varios slots armados listos para lanzar.

Twelve consoles, launched at once

Line up a whole team in the composer and launch it in one action.

04Studios

Your repo, turned into material.

Studios read the repo and give it back as something you can use: streaming documents with real PDF export, diagrams that spill onto the board as loose figures, code trees with highlighted previews and an Obsidian-style markdown vault.

studio-documents.mp416:10
placeholder

Grabar: generacion streaming con el preview en vivo y el export a PDF con paginacion real.

Document studio

Generate documents from the repo with a live preview, then export a real paginated PDF.

studio-diagrams.mp416:10
placeholder

Grabar: un diagrama del repo derramandose como figuras sueltas en el board, estilo ink, y el export a PNG.

Diagram studio

Diagrams of your repo spill onto the board as loose ink figures. Export PNG or .excalidraw.

studio-code.png16:10
placeholder

Captura: arbol de archivos, un preview con syntax highlighting y un nodo de archivo en el board.

Code studio

Browse the file tree, preview code with highlighting and pin files as nodes on the board.

studio-markdown.mp416:10
placeholder

Grabar: el vault con arbol, edicion con autosave y el link graph force-directed moviendose.

Markdown studio

An Obsidian-style vault: file tree, autosaving editor and a force-directed link graph.

05Continuity

Quit the app. Lose nothing.

Close with five consoles running. Reopen and each one relaunches in place and offers to pick up its last conversation, through that CLI's own native resume. Workspaces, skills, project memory and account profiles all live on your disk.

media/resume.mp44:3
placeholder

Grabar: cerrar la app con consolas vivas, reabrir y aceptar el resume de una conversacion.

Sessions that come back

Every workspace is saved on each change. Consoles come back exactly where they were, conversation included.

media/usage.png4:3
placeholder

Captura: la pill de uso por CLI y el apartado Tokens con analytics por dia y agente.

Usage at a glance

A usage pill per CLI and token analytics by day and agent, from your local session logs.

media/accounts.png4:3
placeholder

Captura: perfiles de un CLI con homes aislados, dos cuentas de claude por ejemplo.

Multiple accounts per CLI

Profiles with isolated homes let you run two accounts of the same CLI side by side.

media/memory.png4:3
placeholder

Captura: la memoria per-repo y global, con el boton Push visible.

Project memory

Per-repo and global memory. Nothing reaches a console unless you push it.

06Under the hood

Under the hood

Your agents, your machine, your rules.

FORKPTY

Real terminals

Every console is a full PTY with a controlling terminal: Ctrl-C, job control and full-screen TUIs behave exactly like iTerm.

YOUR PLAN

Your subscription, not API keys

Agents run as the interactive CLIs you are already logged into. Nothing falls outside the plan you already pay for.

ON DISK

Local-first

No backend, no cloud, no Hypervibe account. State lives on your disk as versioned JSON and voice is transcribed on-device.

YOUR ENTER

You have the last word

Agents type. You send. Nothing prepared for you is ever sent for you, and a live console only dies by an explicit, confirmed action.

First run
1

Install your CLIs

Log in to Claude Code, Codex, Gemini or whichever agents you use, the same way you do today. Hypervibe runs the binaries already on your PATH.

2

Open a repo

Point Hypervibe at a folder and it becomes a board: workspaces you switch like tabs, and presets that lay one out in a single tap.

3

Spawn consoles

Add agent consoles as nodes and put them to work. Direct them by voice or keyboard, group them into teams, or leave them on a loop.

07Pricing

One license, your whole fleet. Clear scope, no metering.

annually 2 months free
Plan name Who it is for
$240 / year

$288save $48·vs billing monthly

Get started

What is included

One paragraph on what this tier covers, written once the scope is decided.

  • Feature line one
  • Feature line two
  • Feature line three
  • Feature line four

Pendiente: tiers, precio y trial se definen en docs/decisions.md. Los numeros de arriba son ficticios, puestos solo para probar el switch mensual/anual y el detalle del descuento.

08FAQ

Questions, answered.

Which agents can Hypervibe run?
Claude Code, Codex, Gemini, Grok, opencode and a catalog of 34 CLIs, plus any custom executable you add yourself. If it runs in a terminal, it can live in a node.
Why not tmux and a dozen terminal tabs?
tmux gives you panes. It does not tell you which agent is waiting for you, hand a task from one agent to another, or bring every conversation back when you reopen. Hypervibe keeps the real terminal and adds the board around it: status per console, teams, loops, voice, and a place to plan next to the work.
Is Hypervibe a wrapper around the CLIs?
No. Each console runs the unmodified CLI from your PATH in a real PTY, logged in with your own account. Hypervibe never calls a model itself. It adds the board, voice, teams and loops around the terminal and reads status through the CLI's own hooks.
Do I need API keys?
No. Each console is the real interactive CLI, logged in with your own account. Hypervibe never calls model endpoints itself, so nothing falls outside the subscription you already pay for.
Does my code or voice leave my Mac?
Hypervibe has no backend and no account. All state lives on your disk and voice is transcribed on-device. The only network traffic is whatever the CLIs you run make themselves.
Can an agent do something I did not approve?
Not by default. Nothing auto-typed is auto-sent: flows leave the prompt prepared and you press Enter. Each CLI's auto-approval flag exists as a global opt-in, off by default, and killing a live console always asks first.
Can I add my own CLI?
Yes. Any executable you can run in a terminal can be a console: give it a name and a command and it gets a node like the built-in agents.
What happens to my consoles when I quit the app?
Every workspace persists on disk as versioned JSON, written atomically on each change. Reopen the app and the consoles relaunch in place, each offering to resume its last conversation through that CLI's own native resume.
Can I run more than one account of the same CLI?
Yes. Each CLI can have several profiles, and every profile gets an isolated home, so two accounts of the same agent can work side by side on the same board.
Does voice work offline?
Yes. Speech is transcribed on your Mac and never leaves it. The planner understands commands in your own language, and dictation works the same way.
What are the system requirements?
macOS 14 or later on Apple Silicon.
Is there a Windows, Linux or Intel version?
No. Hypervibe is built natively for Apple Silicon.
Why is it not on the Mac App Store?
Real terminals need to spawn real processes, and the App Store sandbox does not allow that. Hypervibe ships as a direct download instead: it is precisely what makes its consoles real.
How does Hypervibe update?
In the app, through Sparkle. You are told when a new version is available and it installs without going back to the site.

Put your agents on the board.

Download the DMG, open a repo and spawn your first console in under a minute.