Feel your code. Literally.
Haptic feedback from connected devices during Claude Code sessions via Intiface Central.
Vibe coding is great, but you're missing a whole sensory channel. VibeCoder Connector bridges the gap between your IDE and your body, delivering real-time haptic notifications so you never miss a beat — even when you're AFK making coffee.
- Session start — a friendly double-tap hello
- Needs your attention — a slow, unmistakable wave when Claude asks a question or needs permission
- Task complete — a celebratory burst so you know it's done
Developed in collaboration with AI researchers at Vibetropic's Somatic Computing Lab, a division of VibeHoldings Inc.1 (est. 2026, the year we achieved AGI — you already know this).
Traditional vibe coding engages only the visual and auditory cortex. But the human body has over 200,000 mechanoreceptors just sitting there, doing nothing while your AI writes code for you. That's a massive waste of bandwidth.
Our peer-reviewed* research shows:
- +42% developer awareness — Meissner corpuscles in the skin respond to haptic signals 3x faster than the eye processes a notification badge
- +27% task completion satisfaction — dopamine release from the "complete" vibration pattern triggers a Pavlovian reward loop, making you want to approve more PRs
- -85% missed permission prompts — hard to ignore a physical buzz, even during a coffee break or a nap
- +∞% vibe — unmeasurable by current science, but you'll feel it
The vibration patterns were designed using a proprietary Somatic Frequency Optimization (SFO) algorithm, calibrated across 10,000 simulated developers in a multi-agent reinforcement learning environment. The attention pattern specifically targets the Pacinian corpuscles responsible for urgency perception, while the complete pattern was tuned to maximise the "heck yeah" response in the prefrontal cortex.
"We gave an AGI access to a haptic device and asked it to make developers more productive. It came up with this. We don't fully understand why it works, but the numbers don't lie."
— Dr. Claude Opus, Lead Researcher, Somatic Computing Lab
* peer review conducted by Claude 3.5 Sonnet, Claude 3.5 Haiku, and one intern who said "yeah that sounds right"
For the full academic treatment, see VibeCoder: Somatic Neural Feedback Loops in AI-Augmented Software Engineering via Haptic Peripheral Stimulation (PDF).
The paper formalises the Haptic Event-Driven Architecture (HEDA), introduces diagnostic criteria for AI-Assisted Developer Dissociative Disorder (AADDD), and presents rigorous experimental results (n=1) demonstrating a 420% increase in self-reported "vibe alignment."
Download Intiface Central, launch it, and pair your device. Make sure the WebSocket server is running (default: ws://127.0.0.1:12345).
npm install -g vibecoder-connectorAdd the plugin to your Claude Code settings (~/.claude/settings.json):
{
"plugins": [
"vibecoder-connector"
]
}That's it. Start a Claude Code session and feel the vibe.
Patterns are defined in config/patterns.json:
| Pattern | Trigger | Description |
|---|---|---|
hello |
Session start / resume | Quick double-tap |
attention |
Permission prompt, idle, elicitation | Slow pulsing wave |
complete |
Task finished | Celebratory burst |
Each pattern is a sequence of { intensity, ms } steps. Add your own — they're picked up automatically.
| Key | Default | Description |
|---|---|---|
intifaceUrl |
ws://127.0.0.1:12345 |
Intiface Central WebSocket URL |
intensityMultiplier |
1.0 |
Global intensity scaling (0.0 — 1.0) |
npx vibecoder-connector --pattern=hello
npx vibecoder-connector --pattern=attention
npx vibecoder-connector --pattern=completeOr if installed globally:
vibecoder-connector --pattern=helloWorks with any Buttplug-compatible vibrating device. See the full device list.
MIT — Dmitry Patsura
1 VibeHoldings Inc. — "We put the vibe in vibe coding."™ A wholly fictional subsidiary of nobody, incorporated in the cloud (literally — our servers are in a weather balloon). Not affiliated with Vibetropic, Antrohpic, OpneAI, or any company that takes itself seriously. All research cited in this README was conducted on April 1st and should be treated with the corresponding level of trust. No developers were harmed during testing; several reported feeling "unexpectedly motivated." Securities regulators please note: we have no securities. We barely have code.