No. Your training app connects directly to your trainer and controls power, cadence, resistance, and ERG mode. ClickShift connects only to the right-hand Zwift Click v2 and turns button presses into keyboard shortcuts.
Everything you need to know
Frequently asked questions.
ClickShift is intentionally small. Here’s exactly what it connects to, what it controls, and what you need to get riding.
ClickShift includes profiles for MyWhoosh, TrainingPeaks Virtual, and ROUVY. Any other macOS app that accepts keyboard shortcuts can be entered as a Custom app. Zwift is excluded because it supports the Click natively.
macOS requires Accessibility permission for an app to send keyboard shortcuts. ClickShift never reads your typing. With safety mode enabled, it sends shift keys only while your selected training app is focused.
The right controller provides both directions through the + and B buttons without relying on the left controller’s periodic unlock behavior. ClickShift deliberately ignores the left controller.
Yes. It remembers the right controller, reconnects after brief drops or sleep, and starts looking when your selected training app opens. Press + or B once if the controller needs to wake.
Mac impact is negligible. ClickShift waits quietly while the selected training app is closed, scans only until the Click connects, and sends a tiny keepalive during a session. It disconnects when the training app quits.
No. ClickShift has no account, analytics, advertising, or network service. Settings and the remembered controller identifier stay locally on your Mac.
The current download is ad-hoc signed but not Apple-notarized. If macOS blocks it, open System Settings → Privacy & Security, choose Open Anyway, and confirm. The complete source is available on GitHub.