What It Does — Physical Input for Claude Code
SlapClaude is a simple bash script that turns your MacBook's built-in accelerometer into a physical input device for Claude Code. Instead of typing y or pressing Enter to approve tool calls, submit prompts, or confirm actions, you literally slap your laptop. The script monitors for sudden acceleration events and translates them into keyboard input.
Installation is one command:
curl -fsSL slapclaude.com/install | bash
Once installed, the script runs in the background and intercepts acceleration events. A sharp tap on your MacBook's palm rest or lid triggers the equivalent of pressing Enter in your active Claude Code terminal session.
Why It Works — Reducing Cognitive Load
Claude Code's workflow involves frequent approval cycles: "Should I run this command?" "Should I edit this file?" "Should I submit this prompt?" Each requires a mental context switch from reviewing Claude's reasoning to executing the approval.
Physical input bypasses this cognitive overhead. Your brain processes the slap as a simple "yes" action without engaging the language centers needed for typing. This follows Claude Code's recent emphasis on workflow automation, particularly the Auto Mode feature released in preview on March 27, 2026. While Auto Mode handles full automation, SlapClaude provides a middle ground—manual approval with physical immediacy.
How To Configure It — Beyond Basic Slaps
The default installation works immediately, but you can customize the sensitivity and behavior:
- Adjust sensitivity for different desk surfaces or laptop positions
- Map different gestures to different actions (double-tap for cancel, hard slap for force submit)
- Create zone-based triggers where slapping near the trackpad means "approve" but slapping near the keyboard edge means "reject"
Since Claude Code uses MCP servers extensively (mentioned in 25 prior articles), you can integrate SlapClaude with your existing MCP workflow. For example, configure it to only trigger when Claude Code is in a specific state or working on particular file types.
When To Use It — Specific Workflow Scenarios
This isn't for every interaction. Use SlapClaude when:
- Reviewing long sequences of tool calls where you're mostly saying "yes"
- Working through repetitive Claude Code sessions (testing, debugging loops)
- Pair programming with Claude where you want to maintain flow state
- When your hands are already on the laptop (no need to reach for keyboard)
Avoid it for:
- Critical production operations where you need deliberate confirmation
- Situations requiring typed explanations or modifications before approval
- When others might accidentally trigger it (co-working spaces, public transportation)
The Technical Reality — What's Actually Happening
The script uses macOS's Core Motion framework to access the accelerometer. It's essentially a background daemon that:
- Monitors for acceleration spikes above a threshold
- Verifies the pattern matches a "slap" (sharp impulse, not gradual movement)
- Sends a keyboard event to the frontmost terminal window
- Includes debouncing to prevent multiple triggers from a single impact
This aligns with the trend of developers creating physical interfaces for AI tools, similar to how SNARC technology (mentioned in 4 sources) integrates with Claude Code for specialized workflows.
gentic.news Analysis
This development represents the natural evolution of Claude Code's interaction model. As Claude Code appears in 156 articles this week alone (total: 378), developers are clearly seeking efficiency gains beyond traditional keyboard/mouse input. SlapClaude follows Claude Code's March 27 announcement of Auto Mode—while Auto Mode handles full automation, SlapClaude optimizes the manual approval step that remains necessary in many workflows.
The physical input approach connects to broader trends in developer tooling. GitHub Copilot (which competes with Claude Code in 6 sources) has experimented with voice commands, but SlapClaude's tactile approach is uniquely suited to Claude Code's approval-heavy workflow. This also relates to the Model Context Protocol (MCP) ecosystem mentioned in 25 sources—as Claude Code integrates more MCP servers, physical shortcuts become increasingly valuable for managing complex tool call sequences.
Interestingly, this comes just days after our coverage of "Claude Code's New Channels Feature" (March 27), which enables persistent AI agents. Physical approval mechanisms become even more valuable when managing multiple concurrent Claude Code sessions through channels.
Try It Now
Run the install command, then start a Claude Code session:
claude code "Refactor this authentication module"
When Claude asks "Should I run the tests?"—instead of typing y, give your MacBook a firm slap on the side or palm rest. You'll see the approval happen instantly. The first few times will feel strange, but within minutes, you'll notice how much faster your review-approve cycles become.
For developers who use Claude Code daily, this simple physical hack could save hundreds of keystrokes per session while maintaining the deliberate approval that Claude Code's safety model requires.



