This update improves all three:

• Vibetty now runs on Windows, so remote control and voice-driven terminal workflows are no longer limited to macOS and Linux.
• VibeKeys app adds Codex support, including Codex hook mode and a Codex keymap profile for keyboard mode.
• VibeKeys firmware v0.3.1 fixes the default MIC key mapping and improves key release handling on the device.

If you already have a VibeKeys Max, we recommend updating both the desktop software and the device firmware.

Update links:

• VibeKeys app v0.1.9
• Vibetty v0.3.3
• Firmware update guide

Windows support in Vibetty​

Vibetty is the local bridge for VibeKeys Max remote control mode. Vibetty v0.3.3 adds Windows support through ConPTY, and the release includes pre-built binaries for:

• vibetty-windows-x64.exe
• vibetty-macos-arm64
• vibetty-linux-x64

This matters for remote control mode. VibeKeys Max should work with the machine you actually code on, whether that is Windows, macOS, or Linux. With this release, the same voice-driven terminal workflow can run across all three platforms.

On Windows, download vibetty-windows-x64.exe from the release page and run it from PowerShell or Command Prompt with your coding agent command, for example:

.\vibetty-windows-x64.exe -- codex

On macOS or Linux, download the matching binary from the same release and run it with your preferred agent:

./vibetty-macos-arm64 -- claude
# or
./vibetty-linux-x64 -- codex

Codex support in the VibeKeys app​

The VibeKeys app v0.1.9 adds Codex and Claude keymap profiles. The release includes:

• vibekeys-windows-x64.exe
• vibekeys-macos-arm64
• vibekeys-linux-x64

After downloading the VibeKeys app for your platform, install or rename the binary as vibekeys, then check that it runs:

vibekeys --help

The app's Hook Mode reads hook JSON events from stdin and forwards them to the VibeKeys Max display. For Codex hook events, run:

vibekeys codex

To switch the keyboard to a Codex-focused keymap profile, run:

vibekeys profile codex

The codex profile maps CUSTOM to /review + Enter and YOLO to y, so review and approval become physical actions. If you switch back to Claude Code, run:

vibekeys profile claude

Only the CUSTOM and YOLO keys are changed by these profiles, so switching between Codex and Claude Code stays predictable.

Firmware v0.3.1​

The firmware update from v0.3.0 to v0.3.1 focuses on device reliability:

• fixes the default MIC key mapping
• fixes a case where a key release event could be missed during screen refresh
• bumps the firmware version to v0.3.1

The key release fix is especially important for a physical controller. If the display refreshes while you press and release a key, the firmware now handles that state more reliably.

How to update VibeKeys Max​

This update has three parts: update the VibeKeys app, update Vibetty if you use remote control mode, and update the firmware on the device.

1. Update the VibeKeys app​

Download VibeKeys app v0.1.9 for your platform:

• vibekeys-windows-x64.exe for Windows
• vibekeys-macos-arm64 for Apple Silicon Macs
• vibekeys-linux-x64 for Linux x64

This is the tool you use for keyboard configuration, Codex profiles, ASR settings, WiFi settings, and BLE control in keyboard mode. After updating it, check that it runs:

vibekeys --help

2. Update Vibetty​

If you use VibeKeys Max in remote control mode, download Vibetty v0.3.3:

• vibetty-windows-x64.exe for Windows
• vibetty-macos-arm64 for Apple Silicon Macs
• vibetty-linux-x64 for Linux x64

This is the tool that runs the local terminal bridge for Claude Code, Codex, or another terminal program.

3. Update the firmware​

Firmware updates happen on the VibeKeys Max device itself. There are two supported methods:

• OTA update: recommended if your device is working and can connect to WiFi.
• ESP LaunchPad: use this for recovery, factory reset, or when OTA does not work.

Follow the full firmware guide here: Updating VibeKeys Firmware.

Why this update matters​

This update makes VibeKeys less tied to one operating system and one coding agent. Vibetty now reaches Windows users. VibeKeys app now understands Codex workflows. Firmware v0.3.1 improves the physical key behavior on the device itself.

That is the direction for VibeKeys: the repetitive parts of AI coding should become physical, fast, and easy to reach, whether you are using Claude Code, Codex, macOS, Linux, or Windows.

You know the loop: Codex proposes a change and waits, so you reach over and type y. Again. Again. Your sharpest coding tool, and you've turned into a human Enter key. Now y is a keycap you tap, /review is one press, and switching your keypad between Codex and Claude Code is a single command.

Set it up in keyboard mode​

Grab the latest vibekeys CLI (profiles need v0.1.9+), pair VibeKeys Max over Bluetooth, and run one command:

$ vibekeys profile codex
✨ You're with Codex now

That's the whole setup. Now CUSTOM fires /review and YOLO sends y — tap to review, tap to approve, eyes on the diff and hands off the home row. Jump back to Claude Code and vibekeys profile claude puts the keys back. Only those two ever change; your mic, knob, and everything else stay put.

Want Codex's live status on the keypad screen too? Install the plugin — Codex Status Integration.

Or run it wireless​

Prefer to drive Codex from the couch? VibeKeys Max talks to your machine over Wi-Fi through vibetty:

vibetty -- codex

Pair the device at vibekeys.dev/setup.html and steer the whole session — approve, scroll, speak — from across the room. Full steps: Remote Control Mode.

Why Codex, specifically​

Codex runs the same loop all day: prompt, review, approve, repeat. Those repeats are exactly what a dedicated key is for. Profiles just make sure each key means the right thing for the tool you're in — so one keypad covers Codex and Claude Code, with no remapping by hand.

Already have a VibeKeys Max? Update the CLI to v0.1.9+ and run vibekeys profile codex. If you don't, grab one.

A big player validating the category​

For a long time, the idea of a dedicated keyboard for AI coding got the same reaction: "Do you really need that?" When OpenAI ships hardware for exactly this, that question answers itself. The AI coding loop — accept, retry, steer, voice, navigate — is real enough that it deserves its own physical controls. We've believed that since day one, so we're glad to see it.

What was announced​

The OpenAI × Work Louder board is based on Work Louder's Creator Micro 2 macropad, with Codex-specific customization: 13 keys, a knob, a joystick with an on-screen radial menu, touch sensors, RGB lighting, and six configurable layers. It's a capable, power-user macropad.

Two things stand out, though: it's customized for Codex, and at the time of writing it's an announcement — pricing and ship date haven't been finalized. (The Creator Micro 2 it's based on starts at $144.)

The one difference that matters most​

We built VibeKeys with a deliberate choice: don't lock it to a single AI vendor.

Most developers don't live in one tool. You might run Claude Code today, Cursor tomorrow, Codex for one project, Gemini CLI for a quick task. A keyboard customized for one ecosystem ties your hardware to one company's roadmap. VibeKeys remaps to whatever you're using — Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Copilot — so it doesn't become obsolete the day you switch tools.

A few other things a Codex macropad can't do​

• Voice-first input — a dedicated mic key for dictating to your agent hands-free.
• Control from across the room — VibeKeys Max drives your agent wirelessly via the open-source vibetty server, with an OLED screen showing live status. A wired desktop macropad stays at the desk.
• On your desk this week — VibeKeys ships today, from $29, with free worldwide shipping. Not a waitlist.
• Made yours — 3D-printed to order in a range of colors, with custom key icons.

Who each one is for​

If Codex is your single, primary tool and you want the most keys, layers, and RGB you can get, the OpenAI board will be a great fit when it ships.

If you use more than one AI tool, want voice and away-from-desk control, and want something affordable that's available right now — that's VibeKeys.

We put together a full, honest side-by-side here: VibeKeys vs OpenAI's Codex Keyboard.

Either way, the era of physical controls for AI coding is clearly here. We're just glad more people get to feel what it's like — and if you don't want to wait, VibeKeys is shipping today.

What changed​

The hard part of running a terminal app on Windows is the pseudo-terminal (PTY). On Linux and macOS, Vibetty uses a Unix PTY to spawn and talk to the shell. Windows has its own mechanism, ConPTY, and getting it right took two fixes:

• PTY backend. Vibetty now uses portable-pty-psmux, an API-compatible fork of portable-pty. The published portable-pty 0.9.0 has a known ConPTY bug (wezterm#1396) where the spawned process produces no output and ignores input. The fork ships the upstream fix that was never published to crates.io.
• Cursor-position report. Windows ConPTY sends an ESC[6n (cursor position request) on startup and stalls until the host replies. Unix shells don't do this, so macOS was never affected. Vibetty's reader thread now answers with ESC[1;1R on the first read, so cmd, PowerShell, and claude start cleanly.

Running on Windows​

Pre-built releases now include a vibetty-windows-x64.exe binary. From PowerShell or Command Prompt:

# Pre-built binary
.\vibetty-windows-x64.exe -- claude

# Or build from source
cargo build --release
.\target\release\vibetty.exe -- claude

Set your ASR config with $env: in PowerShell:

$env:VIBECODE_ASR_API_KEY = "your_api_key_here"
$env:VIBECODE_ASR_URL     = "https://api.groq.com/openai/v1/audio/transcriptions"
.\vibetty.exe -- claude

Then open http://localhost:3000 and start talking to your agent. The full setup, including the interactive vibetty setup wizard and the browser-side WebVosk mode that needs no API key, is in the README.

Why it matters​

Voice-driven AI coding shouldn't depend on your operating system. With Windows support, the same Vibetty workflow now works the same way across Linux, macOS, and Windows, so you can speak to Claude Code from whatever machine you're on.

The idea is simple: when a developer works with an AI coding agent such as Claude Code or Codex, a small set of actions happens again and again. Accept a change. Reject an answer. Retry a prompt. Continue a task. Compact the context. Scroll through a long diff. Toggle voice input. Switch modes. A vibe coding keyboard puts those actions under physical keys, knobs, and sometimes a status screen.

Why AI coding needs a different interface​

Traditional keyboards were built around typing. Editors added shortcuts for saving files, jumping between panes, running commands, and navigating code. That worked well when the developer was doing most of the direct editing.

AI coding changes the rhythm. The developer is still responsible for direction, judgment, review, and taste, but the interaction becomes more conversational and iterative. You ask the agent to make a change, review the output, approve or reject it, ask for a revision, and keep steering.

That loop is different from typing code line by line. It is closer to operating a second pair-programmer that moves quickly but needs frequent direction. A physical interface helps because the repeated decisions become tactile instead of buried in shortcuts, terminal prompts, or mouse clicks.

What a vibe coding keyboard usually controls​

A useful AI coding keyboard is not just "more buttons." The best layouts are built around the actions developers repeat during agentic coding:

• Accept: approve a suggestion, diff, or generated change
• Reject or Escape: stop the current path and regain control
• Retry: ask the agent to try again or revise an answer
• Continue: move a task forward without retyping the same instruction
• Compact: summarize or compact a long agent session so the context stays manageable
• YOLO or high-trust mode: make an explicit mode shift when you want the agent to act more freely
• Voice input: speak a prompt or longer instruction without reaching for a separate shortcut
• Scroll and navigation: move through long responses, diffs, files, and menus with a knob
• Status: see what the agent is doing without switching windows

That last point matters more as sessions get longer. When your agent is planning, generating, waiting, or blocked, a quick glance at a status screen can be less disruptive than hunting through terminal output.

How it differs from a macro pad or Stream Deck​

A macro pad can send shortcuts. A Stream Deck can launch commands and show visual buttons. Both can be useful, but they start from a general-purpose automation model: you decide what every button means.

A vibe coding keyboard starts from the AI coding loop itself. The physical layout, labels, and defaults are designed around agent control, not generic app shortcuts. That makes it easier to understand and easier to hand to someone who already uses Claude Code, Cursor, Codex, or another coding agent.

The difference is not that a macro pad cannot do some of the same things. It can. The difference is that an AI coding keyboard is opinionated about the workflow from the beginning.

Why physical controls help​

Physical controls are useful when an action is frequent, time-sensitive, or easy to confuse with another action. AI coding has all three.

Accepting a change should feel different from rejecting it. Entering a high-trust mode should be deliberate. Starting voice input should be easy enough that you actually use it. Scrolling through a long agent response should not break your concentration.

That is where tactile controls earn their place. A dedicated key is faster than remembering a shortcut. A knob is more natural for long output than repeated key presses. A clearly labeled mode key reduces the chance of sending the wrong command at the wrong moment. For commands like /compact in Claude Code or similar context-management actions in Codex-style workflows, a physical key also makes the maintenance step harder to forget.

Is it a full keyboard or a keypad?​

It can be either. Some developers want a compact AI coding keypad that sits beside their normal keyboard. Others want a larger keyboard-style control surface that includes more room for status, voice, navigation, and custom labels.

For most people, the important question is not whether it replaces the main keyboard. It usually should not. The better question is whether it gives your AI coding workflow a dedicated physical layer.

That is why VibeKeys has multiple models:

• VibeKeys Pro: a compact wired AI coding keypad with six programmable keys and a knob
• VibeKeys Plus: the same compact idea with Bluetooth, Wi-Fi, and longer desk flexibility
• VibeKeys Max: a larger AI coding console with a status screen, built-in mic, remote mode, open-source firmware, and custom printed case options

If you want the broader category overview, start with the physical vibe coding keyboard guide.

Who should use one?​

A vibe coding keyboard is most useful for developers who already spend real time with AI coding agents. If you only ask an assistant an occasional question, normal shortcuts are probably enough.

It starts to make sense when the agent is part of your daily loop:

• You review generated diffs throughout the day
• You frequently accept, reject, retry, or continue agent output
• You use voice input to describe bugs, architecture, or product behavior
• You work in long Claude Code, Cursor, Codex, Gemini CLI, or OpenCode sessions
• You want a clearer boundary between normal typing and agent control

It is also a practical gift for engineering teams that are adopting AI coding. Unlike generic swag, it maps to a workflow developers are already trying to improve.

The category is still early​

"Vibe coding keyboard" is a new phrase because the workflow is new. Developers are still figuring out which controls deserve hardware and which actions are better left as software.

That is a good reason to keep the design focused. The goal is not to put every possible command on a desk device. The goal is to make the repeated AI coding loop faster, clearer, and more deliberate.

If your agent is becoming a daily collaborator, it may deserve more than a hidden shortcut. It may deserve a physical interface.

Ready to try one? Compare the current VibeKeys models on the vibe coding keyboard landing page, or go straight to VibeKeys Max.

They're beautiful. They rack up thousands of likes. And almost every one of them is a concept render — something that looks incredible in a screenshot but that you can't actually order.

We kept seeing them, and honestly, we love them. We also kept thinking the same thing: someone should actually build this. So we did.

The vibe coding keyboard the community keeps dreaming up​

This concept has become its own micro-genre. Developers and designers keep imagining the same device over and over, each with their own spin, and the renders are genuinely great.

There's @fabianstelzer's clean three-key version, packaged like a luxury product:

Concept by @fabianstelzer. Not affiliated with or endorsed by Anthropic.

There's @Salmaaboukarr's playful translucent-orange "space invader" build, complete with arrow keys, an ENTER bar, and even a microphone key:

Concept by @Salmaaboukarr. Not affiliated with or endorsed by Anthropic.

There's @mattrothenberg's Apple-industrial-design take — milled aluminum, three soft keys, the whole Cupertino look:

Concept by @mattrothenberg. Not affiliated with or endorsed by Apple.

And there's @shiri_shh's maximalist desk console, with a green status display reading TASK: CODE REFACTOR — PROGRESS: 60%, a YOLO MODE key, a model-switcher knob, accept and retry keys, and a mic:

Concept by @shiri_shh — the same "vibe coder needs this in 2026" tweet that kicked off our whole story.

Every one of these is great, and together they point at the same truth: developers really want this thing to exist. The only catch is that they're concept renders. As of today, you still can't buy one.

So we went and built it​

A render racking up thousands of likes is the clearest demand signal you can get. People weren't just admiring these images, they were asking how to own one.

So instead of posting one more concept, we did the unglamorous part: picked real switches, wired up a real knob and display, fit a battery, got it pairing over Bluetooth, wrote the firmware, shipped OTA updates, and put it in a box that arrives at your door.

Same idea everyone loved. We just made it something you can hold.

Meet VibeKeys Max: a real vibe coding keyboard​

This is VibeKeys Max. It's not a render.

Look at what those concept images were all reaching for, and look at what's actually on the desk:

• A status screen that shows what your agent is doing — the maximalist render imagined it; VibeKeys Max has a real LCD on board.
• A YOLO key — the meme everyone drew; here it's a physical key you can press.
• A microphone, built in — talk to your agent instead of typing the prompt.
• A real knob — the model-switcher fantasy, except it's wired up and works.
• An Accept key, a Reject/back flow, ESC — the Allow Once / Always Allow / Reject loop, mapped to keys your thumb finds without looking.

The renders stopped at "wouldn't this be cool." VibeKeys Max boots up, pairs with your machine, and runs the accept-reject-retry loop you do a hundred times a day — by voice or by key, with the screen telling you where things stand. It even has a face: the little robot peeking off the corner is ours.

From a viral tweet to a product you can order​

We didn't pull this out of nowhere. VibeKeys started the same place all those renders did — a tweet that said "vibe coder needs this in 2026" — and then we did the unglamorous part: prototyping, firmware, community feedback, OTA updates, and a manufacturing line.

The difference between us and the timeline full of concepts is simply that we kept going after the screenshot looked good.

If you've been staring at those renders wishing one of them were real: one of them is.

Get the real thing​

• VibeKeys Max — the full vision the concepts were chasing: LCD status screen, built-in mic, knob, YOLO key, voice and remote workflows. This is the one to get.
• VibeKeys Plus — the same core flow in a tighter package.
• VibeKeys Pro — production-ready and the most affordable way to put a real accept/reject/retry keypad on your desk today.

Looking for a developer gift? VibeKeys Max is the rare one people actually use — grab one for the coder in your life, or order a batch as company swag your engineers will keep on their desks.

Stop scrolling past the renders. Put a real vibe coding keyboard on your desk →

We make three models — Pro, Plus, and Max — each designed for a different setup and budget. This post breaks down what sets them apart so you can pick the right one.

The Quick Overview​

VibeKeys Pro — The Starting Point​

$29 USD | USB-C wired | 6 keys + knob

Pro is the entry point. Six programmable keys and a rotary knob give you tactile shortcuts for the actions you repeat most: accept, reject, retry, YOLO mode, voice input, and usage stats. The clicky mechanical switches feel deliberate, and the compact layout keeps everything within reach.

The wired USB-C connection means zero latency and no charging — just plug in and go. PBT keycaps with laser-etched legends keep the labels readable over time.

Best for: Developers who want a simple, affordable companion for AI coding at a fixed desk setup. If you work at one station and want physical buttons for Claude Code, Cursor, Copilot, or Codex without any setup complexity, Pro is the right call.

VibeKeys Plus — Cut the Cable​

$49 USD | Bluetooth + Wi-Fi | 6 keys + knob

Plus takes the same compact 6-key layout from Pro and adds wireless connectivity. Bluetooth for direct pairing, Wi-Fi for more flexibility across your workspace. The 15-day battery life means you're not constantly reaching for a charger.

The key layout and workflow stay intentionally close to Pro — upgrading doesn't mean relearning. It also adds Linux support, which Pro doesn't have.

Best for: Developers who want the Pro experience without a cable. If you move between setups, prefer a cleaner desk, or work on Linux, Plus is the natural upgrade. The $20 premium over Pro buys you wireless freedom and a longer platform support list.

VibeKeys Max — The Full Experience​

$69 USD (normally $99) | Bluetooth 5.0 + Wi-Fi + USB-C | Full keyboard + knob + OLED + mic

Max is a different category. It's not just a keypad — it's a dual-mode device. In Keyboard Mode, it works at your desk as a full ergonomic keyboard interface for vibe coding. In Remote Mode, the built-in microphone lets you interact with Claude Code from across the room using voice.

The OLED display shows real-time status — what Claude Code is doing, build progress, mode indicators. The firmware is fully open source, and you can update it over the air via Wi-Fi.

A great gift for developers. Every Max unit is 3D printed to order, so you can make it personal. Choose your case color — match their setup, their favorite color, or just make it stand out. Then add custom text: a name, a team motto, a inside joke, whatever makes it theirs. It's a thoughtful, useful gift that most developers wouldn't buy for themselves but will actually use every day.

Best for: Developers who want a complete AI coding interface that works both at the desk and away from it. If you use Claude Code's voice features, want an OLED status display, or care about open source firmware you can customize and extend, Max is the one. Also the best pick if you're shopping for a developer who already has everything — the customization makes it one-of-a-kind.

How to Choose​

Start with your workspace:

• Fixed desk, simple needs → Pro ($29). Plug in, map your keys, done. No charging, no pairing, no complexity.
• Mobile or multi-desk → Plus ($49). Same compact concept, now wireless. The 15-day battery makes it practical day-to-day.
• Voice-first or remote coding → Max ($69). The built-in mic and dual-mode design let you code from the couch, the whiteboard, or anywhere in the room.

Start with your budget:

All three include free worldwide shipping. Pro at $29 is an easy way to try the VibeKeys concept. Plus at $49 is the sweet spot for wireless. Max at $69 (currently 30% off) is the full package with features you won't find in the other two — OLED, mic, open source firmware, and customization.

They All Share the Same DNA​

Every VibeKeys model is designed around the same idea: vibe coding works better with physical controls. Whether you're accepting AI suggestions, triggering voice input, or scrolling through diffs, a dedicated key beats a keyboard shortcut. The three models just give you different levels of that experience.

Pick the one that matches how and where you code. You can always upgrade later — the workflow transfers.

Ready to order? Check out VibeKeys Pro, VibeKeys Plus, or VibeKeys Max.

Keyboard Mode​

VibeKeys Max now suppots Keyboard mode by default. Pair over Bluetooth, and VibeKeys Max becomes a dedicated Claude Code controller. Every key sends input directly to your computer. The defaults are tuned for Claude Code workflows — /compact, page scroll, accept, escape, YOLO — and every key is remappable if you need something different.

No server. No WiFi. No setup beyond Bluetooth pairing.

Keyboard Mode guide | Customize Key Mappings

Live Claude Code Status on the Screen​

When you are deep in a coding session with Claude Code, context switching is expensive. Checking the terminal to see if Claude is still thinking — or already waiting for you — pulls you out of whatever you were reading, reviewing, or planning next.

The VibeKeys Max screen now shows Claude Code's status in real time. You can see whether it is thinking, generating, planning, or done and waiting for your input. It turns the keyboard into a passive status indicator — like a build light on your desk, but for your AI coding agent. A quick glance is all it takes to stay in sync without breaking your flow.

Claude Code Status Integration guide

OTA Firmware Updates​

Until now, updating firmware meant finding a USB cable, opening a flashing tool, and going through a multi-step process. That friction meant most users stayed on whatever version shipped from the factory — even when newer firmware brought real improvements.

OTA updates remove that barrier entirely. If your device is connected to WiFi, you can update the firmware wirelessly from your browser in a few minutes. No cables, no drivers, no flashing tools. This means we can ship improvements faster and you can actually receive them.

The USB-based ESP LaunchPad method is still available for recovery and factory resets.

Updating Firmware guide

For Existing Users (Received Before April 10th)​

If you already have a VibeKeys Max, here is how to get all the new features.

Layout change: The positions of the "Plan" key and the "Delete" key have been swapped in the latest firmware. To apply this and all other updates, please reflash the firmware using the ESP LaunchPad method.

After reflashing:

• Your device will default to keyboard mode — just pair over Bluetooth and you are ready to go
• To enable real-time Claude Code status on the screen, install the plugin by following the Claude Code Status Integration guide
• To customize key mappings, see the Customize Keys guide

Enjoy vibe coding!

Claude Code has built-in voice support. With the right key mapping on VibeKeys Pro, you can trigger it and speak hands-free — no keyboard reach required.

Voice Typing and Vibe Coding​

Typing is still a context switch. You stop thinking about the problem, shift to the keyboard, form sentences with your fingers, and then go back to thinking. Voice typing removes that switch. You stay in idea mode the whole time.

For vibe coding specifically — where you are describing architecture, asking for changes, or walking Claude through a problem — speaking feels more natural than typing. You think in sentences, not keystrokes.

The challenge is that voice input on a laptop still requires you to reach for the keyboard to start and stop recording. VibeKeys Pro solves that with dedicated physical controls.

The Setup​

Step 1: Download the VibeKeys Configurator

Download the VibeKeys Configurator for macOS or Windows. Launch the app and it will detect your connected VibeKeys Pro automatically.

Then configure two key mappings:

Step 2: Voice key → /voice + Enter

Assign your dedicated voice button to send the /voice command followed by Enter. This enters Claude Code's voice mode in one press.

Step 3: Knob press → Space (hold)

Once in voice mode, hold down the knob while you speak. Claude Code uses the spacebar as a push-to-talk trigger — hold to record, release to send.

This key map shows one way to customize VibeKeys Pro for Claude Code voice mode, with dedicated buttons for voice entry, usage prompts, retry, and navigation.

The Workflow​

1. Press the voice key — Claude Code enters voice mode
2. Hold the knob while speaking your prompt
3. Release the knob — transcription is sent
4. Repeat

No keyboard. No mouse. Just speak and vibe.

You can see the workflow in action here:

Watch on YouTube

Why This Works Well​

The knob is a natural push-to-talk control. It sits under your thumb, requires no visual confirmation, and the physical feedback tells you when you are recording. Compared to reaching for a keyboard shortcut mid-thought, it keeps the speaking flow intact.

The voice key handles the mode switch so you never have to type /voice manually. One press and you are ready to speak.

This is the kind of workflow VibeKeys Pro was built for — turning repetitive interactions into physical muscle memory.

It all started with a single tweet.

One day in early 2026, shiri_shh posted something simple: "Vibe coder needs this in 2026"

Attached was an image of a keypad with AI capabilities. That's it.

But those 6 words hit different.

We looked at it and thought: Wait. This isn't just a meme. This is actually incredibly useful. The idea of an AI coding keypad that streamlines programming workflows felt like the natural evolution of how we should interact with code. No more endless keyboard shortcuts. No more context switching. Just flow.

We decided to share the idea on Reddit and see if others felt the same way. We posted: "Is this actually something people would use?"

Community Validation​

The response blew us away.

Developers got it immediately. They saw the same pain points we did every single day: repetitive keystrokes, interrupted flow, and the mental load of remembering hundreds of key combinations. The feedback was clear: this wasn't just a fun idea. It was something people genuinely wanted.

So we started building.

From Prototype to Product​

We locked ourselves in, wrote the code, and wired up the hardware. After days of intense development, we had something. It wasn't polished. It was raw and experimental. But it worked.

We shared the demo, and the community responded again.

Then came the question that opened up a bigger direction: Should we add a mic?

With a built-in microphone, you would not need to stay tethered to your computer. You could work from a distance, use voice commands naturally, and let the keypad act as a more independent device. That was the moment VibeKeys Max really started to take shape.

VibeKeys Max became our vision for the ultimate AI coding keypad: physical controls for Claude Code, Codex, and Cursor, combined with voice and AI.

Two Paths Forward​

At the same time, we knew not everyone wanted to wait for that future. Some developers wanted something they could use right away.

So we created VibeKeys Pro.

Built on top of proven foundations and shaped by community feedback, VibeKeys Pro is the production-ready AI coding keypad you can order today. It takes the core idea of vibe coding and turns it into a practical tool for real development workflows.

• VibeKeys Max: our forward-looking version with voice and remote workflows
• VibeKeys Pro: available now, production-ready, and ready to ship

The Story Continues​

The project keeps evolving through fast iteration, community feedback, and hands-on experiments with how developers want to work with coding agents.

At the end of the day, this is not just our product. It is a collaboration with every developer who has thought, "there has to be a better way to code."

If you want to follow the journey:

• Explore VibeKeys Pro
• Learn about VibeKeys Max
• Follow us on X