Release 0.1.1 is the boundary for this guide
Ultragrip’s public release manifest was checked on 29 July 2026. It identified version 0.1.1, released on 22 June 2026, with a universal macOS disk image and a 64-bit Windows installer. There is no Linux artifact in the current manifest.
That distinction matters because the development branch contains controller layers and optional tool adapters that were added after the 0.1.1 release tag. They are not documented here as downloadable features. This guide follows the tagged 0.1.1 source, the live manifest, and current Claude Code shortcut documentation.
Ultragrip is beta software. The macOS and Windows builds are unsigned. Expect operating-system warnings, and decide whether you trust the source before overriding a security control.
What you need
- A macOS or 64-bit Windows computer.
- Claude Code installed and working independently of Ultragrip.
- A controller recognized by the operating system and Ultragrip’s input layer.
- The keyboard and pointer kept within reach during setup.
- On macOS, Accessibility permission for synthesized keyboard and pointer input.
- For voice on macOS, Microphone and Speech Recognition permission plus an internet connection for AI enhancement.
Controller compatibility depends on the controller, connection mode, driver, and operating system. The application reports the detected controller in its status panel. That status is the useful test. A brand name alone is not evidence that a particular model or wireless mode will work.
1. Download the manifest-backed installer
Open the Ultragrip download page. It fetches the release manifest and only creates a download link when the corresponding artifact exists.
On macOS, open the disk image and move Ultragrip to Applications. Version 0.1.1 is not signed or notarized. Apple explains that overriding Gatekeeper for an unidentified developer carries risk. If you choose to proceed after attempting to open the app, use System Settings, Privacy & Security, then Open Anyway. Read Apple’s safety guidance before doing so.
On Windows, run the MSI installer. The unsigned beta may produce a publisher or reputation warning. Do not treat the presence of a file on this site as independent security review.
There is no Linux artifact in the current manifest, so the download page correctly shows Linux as coming soon. Instructions for an AppImage do not apply until an artifact exists.
2. Grant only the permissions you need
On macOS, open System Settings, Privacy & Security, then Accessibility, and allow Ultragrip. Restart the app after changing permission. Without Accessibility access, the controller can appear in the Ultragrip interface while synthesized input fails to reach Claude Code.
Screen Recording is separate. Version 0.1.1 uses it to read active-window titles for context. The app can still detect the foreground application without a title when permission is unavailable. Grant it only if you want that context feature.
Voice also requires Microphone and Speech Recognition access. Voice dictation is macOS-only in 0.1.1. Windows users can use the controller mappings, but the released app reports native dictation as unsupported.
3. Connect and verify the controller
Connect by cable first if possible. A wired test removes Bluetooth pairing and battery state from the initial diagnosis.
Launch Ultragrip and check the controller status panel. Press each face button and move each stick while watching the interface. If the app does not display a controller:
- Confirm that the operating system sees it.
- Disconnect other controllers and reconnect the intended device.
- Try a direct USB port and another data-capable cable.
- Restart Ultragrip after connecting.
- If wired input works, test Bluetooth as a separate change.
Do not move on until the status panel reacts consistently. Testing mappings while detection is intermittent produces confusing results.
4. Select the Claude Code profile
Open Claude Code in a terminal, focus its input area, and select the Claude Code profile in Ultragrip. Version 0.1.1 synthesizes ordinary keyboard or pointer actions. It does not install a Claude Code keybinding file.
Use a harmless prompt for the first test. The face-button names below include the PlayStation position first and the Xbox letter second.
| Controller input | Shipped 0.1.1 output | Claude Code use |
|---|---|---|
| Cross / A | Enter | Submit input or confirm the selected option |
| Circle / B | Escape | Cancel input, reject, or interrupt where Claude handles Escape |
| Square / X | Control+C | Standard interrupt |
| Triangle / Y | Shift+Tab | Cycle permission mode |
| L1 / LB | Up Arrow | Move up or recall earlier input, depending on context |
| R1 / RB | Down Arrow | Move down or advance through input history |
| D-pad | Arrow keys | Navigate the current input or menu |
| Left stick | Arrow keys | Directional navigation |
| Right stick | Pointer movement | Move the system pointer |
| Start / Menu | Inserts / | Open Claude Code command completion when the prompt is empty |
| Select / View | Inserts @ | Open file-path completion |
| L2 / LT | Holds Control | Modifier used with another synthesized input |
| R2 / RT | Voice capture on macOS | Hold to capture speech, then release |
Claude Code behavior is contextual. For example, Up and Down move within multiline input before they reach command history. Escape and Control+C also have distinct roles in current Claude Code. Check the official interactive-mode reference if a synthesized shortcut no longer matches the installed Claude Code version.
The release does not include the later L2 semantic command layer, 350 ms interrupt hold, double-tap dictation lock, safe adapter installer, repair flow, or guarded restore flow. Those features exist on the development branch, not in the 0.1.1 binary.
5. Test one action at a time
Start with the least destructive sequence:
- Type a short prompt with the keyboard but do not send it.
- Press Cross or A and confirm that Enter is synthesized.
- Recall or edit a prompt with L1, R1, and the D-pad.
- Open a harmless confirmation and test Circle or B.
- Start a disposable response and test Square or X as Control+C.
- Test
/and@only from an empty draft so inserted text is visible.
If the Ultragrip interface reacts but Claude Code does not, verify that the terminal is focused. On macOS, recheck Accessibility permission. If input reaches a different application, stop and restore focus before continuing.
6. Configure voice on macOS
Voice dictation is macOS-only in 0.1.1. Hold R2 to start capture and release it to stop. The released gesture is hold-to-talk; double-tap locking was added later and is not present in this binary.
The native macOS speech recognizer produces the transcript. Ultragrip can then send that text either through the hosted enhancement service during the seven-day trial or with Pro, or directly to Gemini when you provide your own API key. The resulting text is typed into the focused application.
This means three separate stages can fail: local speech capture, AI enhancement, or text injection. Diagnose them in that order. Confirm that a transcript appears before changing API settings. Confirm enhancement before testing injection in an important prompt.
Do not dictate secrets, credentials, private source code, or personal data unless you have reviewed the relevant privacy terms and AI-provider data flow. A local microphone does not make the enhancement request local.
7. Understand Free, trial, and Pro
The released app starts a seven-day full-feature trial from first install without requiring a card. After the trial, Free keeps the Claude Code profile and allows bring-your-own-key Gemini enhancement. Pro is listed at €4.99 per month and unlocks the other tool profiles plus hosted enhancement.
Subscription is linked to a device identifier. Open the subscription page from the desktop app so checkout receives that identifier. There is no email-account registration step in the current flow.
Treat the plan description as an entitlement boundary, not a performance promise. Ultragrip has not published a controlled speed, accuracy, productivity, or ergonomic-outcome test.
Updating and rollback
Version 0.1.1 does not implement automatic updates. Check the download page for a later manifest version and install it manually.
The application sends keyboard and pointer input to other software. Keep your keyboard available, pause mapping when behavior is unexpected, and test a new release in a disposable session before using it in a sensitive terminal.
Ergonomic scope
A controller redistributes some actions. That does not establish that it is more comfortable or safer for you, and repeated thumb input can create its own workload. Ultragrip has not been clinically tested or shown to prevent repetitive strain injury.
Use the developer input ergonomics guide to evaluate fit, placement, work routine, and symptoms without treating a device purchase as medical care.
Verification sources
This guide was substantively reviewed on 29 July 2026 against:
- Live Ultragrip release manifest
- Ultragrip 0.1.1 tagged source
- 0.1.1 mapping table
- 0.1.1 platform dictation bridge
- Claude Code interactive-mode shortcuts
- Apple guidance for apps from unidentified developers
Recheck the manifest and release notes when a new binary is published. Development-branch behavior is not release evidence.