A new Claude Code plugin called VibeClaude is taking 'vibe coding' unusually literally by linking Claude's coding activity to a vibration-capable device.
The open-source project, published on GitHub by developer transkatgirl yesterday, uses Claude Code hooks, Intiface Central and the Buttplug client to turn actions such as tool calls, edits and completed tasks into physical vibration patterns.
The project is not an official Claude feature. Its README describes VibeClaude as a port of an existing OpenCode project designed for Claude Code's function-hooks system, which the developer identifies as an early-access API.
The repository says it was built against Claude Code 2.1.291 and requires Node.js 22 or newer.
How Vibe Coding Became a Physical Feedback System
The plugin is designed to translate activity inside a Claude Code session into signals sent to a connected device. The system runs through several layers.
Claude Code sends events to the plugin's hooks module, which passes small event messages to a local daemon. That daemon communicates with Intiface Central through a WebSocket connection, while Intiface handles the connection to the paired Bluetooth-enabled device.
The developer says the system does not send the model's actual conversation text to the daemon. Instead, the hooks module reduces activity to event information such as sizes and identifiers before sending it to the local service.
when you're Claude Coding, have you ever thought: "i waanna have Claude fuck me a lil bit while i waitt~"?
— kat (@transkatgirl) October 7, 2026
now you can have true vibe coding with VibeClaude! feel every action and come back begging for more!
it even supports multi-agent and multi-session workflows for a more… pic.twitter.com/xP8JOET2J1
That means different things happening during a coding session produce different patterns.
When Claude's thinking or text streams, VibeClaude sends short pulses whose intensity varies with the speed of the model's output. A successful tool call produces a slower pulse, while a failed or rejected tool call produces a sharper one.
Writing or editing code is handled differently, with the device maintaining a steady vibration while the operation is being written and applied.
Permission requests also have their own pattern, with three pulses repeating while the prompt remains unanswered. When a coding turn ends, the device produces three pulses at maximum intensity according to the project's documentation.
The developer says the system can handle multiple Claude Code sessions and subagents at the same time. When several sessions are active, the strongest signal takes priority rather than allowing every event to play simultaneously.
Vibe Coding Plugin Comes With Some Important Limits
The README is unusually detailed about what VibeClaude cannot detect perfectly.
Claude Code does not always expose its internal activity to plugins.
Thinking is only available when Claude Code makes that content visible to the user, meaning some headless runs will not generate the corresponding physical feedback. Tool output is another limitation because the plugin is not told about command output as it appears.
Permission prompts are also approximate. Claude Code controls the prompt itself and does not tell the plugin exactly when a user approves it. As a result, the vibration associated with a permission request can continue until the relevant tool finishes or fails.
There is a practical control built in for anyone who finds the default settings too strong. The /intiface-intensity command applies a multiplier to the entire system, with values ranging from zero to one. The setting is remembered until changed.
The developer also includes a mock Intiface server for people who want to test the software without a physical device. The project can simulate a controller and print the vibration levels it would have produced.
Privacy is another point addressed by the repository. According to its documentation, device commands are sent only to the Intiface address configured on the user's own machine. The daemon listens on the local loopback address, and the project says it collects no telemetry.
VibeClaude is released under the MIT licence. The repository also makes clear that the project remains limited to vibration-based feedback for now. It does not yet support other device outputs such as rotation, oscillation or linear movement.
For a technology trend that usually refers to writing software by describing what you want in natural language, this particular interpretation of 'vibe coding' is certainly hard to misunderstand.
