Mouse-side-button voice input for VibeCoding.

中文文档:README.zh-CN.md

AI adaptation guides:

• English: docs/AI_ASSISTANT_DEPLOYMENT.md
• 中文:docs/AI_ASSISTANT_DEPLOYMENT.zh-CN.md
• AI debug runbook: docs/AI_DEBUG_RUNBOOK.md

VibeMouse binds your coding speech workflow to mouse side buttons:

• Front side button: start/stop recording
• Rear side button while idle: send Enter
• Rear side button while recording: stop recording and route transcript to OpenClaw

Core goals are low friction, stable daily use, and graceful fallback when any subsystem fails.

The runtime is event-driven and split by responsibility:

1. vibemouse/main.py
   • CLI entry (run / doctor)
2. vibemouse/app.py
   • Orchestrates button events, recording state, transcription workers, and final output routing
3. vibemouse/mouse_listener.py
   • Captures side buttons and gestures (evdev first, fallback path available)
4. vibemouse/audio.py
   • Records audio to temp WAV
5. vibemouse/transcriber.py
   • SenseVoice backend selection and transcription
6. vibemouse/output.py
   • Text typing / clipboard / OpenClaw dispatch, with fallback and reason tracking
7. vibemouse/system_integration.py
   • Platform adapter boundary (Hyprland now, Windows/macOS extension points prepared)
8. vibemouse/doctor.py
   • Built-in diagnostics for env, OpenClaw, input permissions, and known conflicts

sudo apt update
sudo apt install -y python3-gi gir1.2-atspi-2.0 portaudio19-dev libsndfile1

sudo pacman -Syu --needed python python-pip python-gobject portaudio libsndfile

python3 -m venv .venv
source .venv/bin/activate
pip install -U pip
pip install -e .

export VIBEMOUSE_BACKEND=funasr_onnx
export VIBEMOUSE_DEVICE=cpu
vibemouse

Default install is ONNX-first for smaller deployment footprint.

• Optional PyTorch backend (GPU/advanced fallback): pip install -e ".[pt]"
• Optional Intel NPU dependencies: pip install -e ".[npu]"

bash scripts/auto-deploy.sh --preset stable

This command bootstraps .venv, installs VibeMouse, generates service/env files, enables systemd --user service, and runs vibemouse doctor.

Available presets:

• stable: balanced daily-driver defaults
• fast: lower debounce + higher OpenClaw retries
• low-resource: lower background footprint defaults

Examples:

# High reliability profile
bash scripts/auto-deploy.sh --preset stable
# Keep resources low
bash scripts/auto-deploy.sh --preset low-resource
# Custom OpenClaw target assistant
bash scripts/auto-deploy.sh --preset stable --openclaw-agent ops

• VIBEMOUSE_FRONT_BUTTON default: x1
• VIBEMOUSE_REAR_BUTTON default: x2

State matrix:

• Idle + rear press -> Enter (VIBEMOUSE_ENTER_MODE)
• Recording + rear press -> stop recording + OpenClaw dispatch

If your hardware labels are reversed:

export VIBEMOUSE_FRONT_BUTTON=x2
export VIBEMOUSE_REAR_BUTTON=x1

OpenClaw route is explicit and configurable:

• VIBEMOUSE_OPENCLAW_COMMAND (default openclaw)
• VIBEMOUSE_OPENCLAW_AGENT (default main)
• VIBEMOUSE_OPENCLAW_TIMEOUT_S (default 20.0)
• VIBEMOUSE_OPENCLAW_RETRIES (default 0)

Dispatch behavior:

• Fast fire-and-forget spawn to avoid blocking UI interaction
• Route result includes reason (dispatched, dispatched_after_retry_*, spawn_error:*, etc.)
• Clipboard fallback if command is invalid or spawn fails

Deployment tip: if you run your own local assistant setup, set VIBEMOUSE_OPENCLAW_AGENT to your own assistant ID.

Run diagnostics:

vibemouse doctor

Apply safe auto-fixes first, then re-check:

vibemouse doctor --fix

Current checks include:

• Config load validity
• OpenClaw command resolution + agent existence
• Microphone input availability
• Linux input device permissions / side-button capability
• Hyprland rear-button Return bind conflicts
• systemctl --user service activity

Current auto-fixes (--fix) include:

• Auto-disable conflicting Hyprland side-button Return binds
• Attempt to restart inactive vibemouse.service

Exit code is non-zero when any FAIL check exists.

The deploy command is scriptable and can be used directly:

vibemouse deploy --preset stable

Useful flags:

• --preset stable|fast|low-resource
• --openclaw-command "openclaw --profile prod"
• --openclaw-agent main
• --openclaw-retries 2
• --log-file ~/.local/state/vibemouse/service.log
• --skip-systemctl
• --dry-run

Persistent debug logs (recommended):

tail -f ~/.local/state/vibemouse/service.log

Full configuration source of truth: vibemouse/config.py.

When users report that recording, right-button gestures, and Enter all fail together, the most common root cause is mouse side-button event mismatch, not a dead service.

Typical failure pattern:

• Service is active, but button actions never trigger.
• Hyprland workspace commands still return ok when run manually.
• User perception: "all features are broken".

Real root causes we hit:

1. Side-button codes were only matched as BTN_SIDE/BTN_EXTRA.
2. Some mice emit BTN_BACK/BTN_FORWARD aliases instead.
3. Runtime env had action mappings, but listener never recognized raw events.

Current fix in code:

• x1 accepts {BTN_SIDE, BTN_BACK}
• x2 accepts {BTN_EXTRA, BTN_FORWARD}

Fast verification order (recommended):

1. systemctl --user is-active vibemouse.service
2. hyprctl dispatch workspace e-1 and hyprctl dispatch workspace e+1
3. vibemouse doctor
4. Confirm runtime env from /proc/<MainPID>/environ:
   • VIBEMOUSE_GESTURE_TRIGGER_BUTTON
   • VIBEMOUSE_GESTURE_LEFT_ACTION
   • VIBEMOUSE_GESTURE_RIGHT_ACTION
   • VIBEMOUSE_FRONT_BUTTON / VIBEMOUSE_REAR_BUTTON

If (1)-(3) pass but buttons still do nothing, debug listener code-path first.

Check Hyprland-level hard bind conflict in ~/.config/hypr/UserConfigs/UserKeybinds.conf and remove lines like:

bind = , mouse:275, sendshortcut, , Return, activewindow
bind = , mouse:276, sendshortcut, , Return, activewindow

Then reload:

hyprctl reload config-only

openclaw agent --agent main --message "ping" --json
vibemouse doctor

sudo usermod -aG input $USER
# relogin required

Use this guide when adapting to Windows/macOS or custom environments:

• docs/AI_ASSISTANT_DEPLOYMENT.md
• docs/AI_ASSISTANT_DEPLOYMENT.zh-CN.md
• docs/AI_DEBUG_RUNBOOK.md

It contains architecture contracts, dependency download links, adaptation workflow, and a prompt template for autonomous platform adaptation.

Source code is licensed under Apache-2.0. See LICENSE.

Third-party and model asset notices: THIRD_PARTY_NOTICES.md.