DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to feel Claude Code turn events through a vibration device with Vibeclaude

Install the plugin, pick a device in Intiface Central, and feel Claude Code's activity as it runs.

Reverse engineering. The device is body-worn and output can be intense, so set the intensity low before the first run and stop with /intiface-disconnect if anything is uncomfortable.

Who it is forA Claude Code user with a vibration-capable Intiface device who wants physical feedback while a long coding session runs.

The problemWatching the screen for every turn end, tool result or error is tedious, and a silent session gives no sign of what Claude is doing.

The outcomeClaude Code events play on the selected device, with intensity set to a level you choose.

What you need first

  • Claude Code with function-hooks plugin support (the README says it is an early-access API, built against 2.1.291)
  • Node.js 22+ available as node on your PATH
  • Intiface Central installed, with its WebSocket server running at ws://127.0.0.1:12345
  • A vibration-capable controller paired in Intiface Central
  • A private setting where you are comfortable using the device

Steps

  1. Run git clone https://github.com/transkatgirl/vibeclaude.git ~/.claude/vibeclaude and then cd ~/.claude/vibeclaude && npm install.
  2. Start Intiface Central and press the server start button.
  3. Start Claude Code with claude --plugin-dir ~/.claude/vibeclaude, then run /intiface and select a vibration-capable device from the scan results.
  4. Run /intiface-intensity 0.5 to halve every pattern, or leave it at the default of 1.0.
  5. Start a coding task and check that the device pulses when Claude streams text and when the turn ends.

Prompt for your agent

Install the plugin from the transkatgirl/vibeclaude repo into ~/.claude/vibeclaude, run npm install there, and load it with claude --plugin-dir. Report the output of /intiface-intensity with no argument and confirm that the selected device is <device name> in the /intiface list. Verify that the daemon answers after running node daemon/daemon.mjs status.

Caveat. Thinking is only felt where Claude Code shows it, and tool output is not felt as it prints, so some events will not produce a pulse.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page