v1.0.4

Changes

• Narrowed the connection-slot select in the header so the full header fits within the minimum window width, including in English with the update chip visible while connected.
• Long connection-slot names are now truncated with an ellipsis instead of being clipped.

Full Changelog: v1.0.3...v1.0.4

v1.0.3

Changes

• Raised the minimum window width from 1130 to 1165.

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Fixes

• macOS: the HDMI capture preview now works in the packaged app. The release build was missing the camera entitlement and usage description, so the hardened runtime denied camera access outright. The app now asks for camera permission the first time the preview starts.
• macOS: added the local-network usage description so the Wi-Fi (TCP) connection to a Pico works with the local-network privacy prompt on macOS 15+.

Linux

• The deb and rpm packages now set up device permissions on install — no manual configuration needed anymore:
  • udev rules granting access to the Pico's serial port, a USB Pro Controller and the dongle identities
  • CAP_NET_RAW on the app binary so the Bluetooth features (Pico link, Pro Controller 2 recording) work without root, including the loader configuration that file capabilities require
• The AppImage cannot run install scripts; the README documents the manual udev setup, and Bluetooth users should prefer the deb/rpm packages.

Full Changelog: v1.0.1...v1.0.2

v1.0.1

Fixes

• Firmware install: remount the BOOTSEL drive before writing (macOS). Leaving the board in BOOTSEL mode for a while let the OS's cached view of the drive drift from what the device actually serves, and the install could then fail until the board was replugged. The drive is now remounted right before the write, which resets that state automatically. The remount is best effort — if it isn't possible, the write proceeds as before.
• Firmware install: write failures now include a hint to replug the device and try again.

Full Changelog: v1.0.0...v1.0.1

v1.0.0

The first public release of Karakuri Pad — a free, open-source desktop app that turns a Raspberry Pi Pico W / Pico 2 W into a Nintendo Switch controller, and a Pro Controller 2 into a USB gamepad for PC / Mac.

Website & manuals: https://karakuri-pad.com

Macro mode (Bluetooth / Wi-Fi)

• Drive the console directly from the on-screen controller UI, with an HDMI capture preview beside it
• Build macros by drag & drop and loop them — loops run on the Pico itself, so idle farming keeps going with the app closed
• Record input from a Pro Controller (USB) or a Switch 2 Pro Controller (BLE) straight into a macro, timing included
• Passthrough: forward your own controller input straight to the console
• Connect over Bluetooth (default, no router needed) or Wi-Fi (TCP)

Dongle mode

• Flash the Pico into a USB dongle that turns a Pro Controller 2 into a USB gamepad for PC / Mac or the Switch itself
• Four output identities: SInput / DualShock 4 / Switch / Pro Controller — gyro and rumble keep working in all but the Switch identity
• A standalone macro recorder records and replays input on the controller alone, no app needed

Everything inside the app

• Firmware flashing (BOOTSEL) and all configuration happen in the app — no toolchain, no terminal
• Japanese and English UI
• Checks for updates on startup and upgrades itself in one click

Installation notes

• macOS: signed and notarized — launches without warnings
• Windows: unsigned; SmartScreen will warn on first run. Choose "More info" → "Run anyway" (guide)
• Linux: serial/HID/Bluetooth access needs a few permissions — see the README

Notes

• This is an unofficial tool with no affiliation to Nintendo
• Automation in online play risks having your account suspended — keep it to offline, solo play
• Use at your own risk