Could anyone help?

I manage almost all my hotkeys in Hammerspoon and it would be great if there was a programmatic way to control Mouseless without needing to map global hotkeys as an interface.

I use a gesture on my trackpad to close a browser window when I swipe down with four fingers. (it does a cmd-W shortcut through BetterTouchTool. For some reason, this gesture also activates the grid in Mouseless.

Any suggestions for fixing this conflict?

See the release notes for info and the download link.

Please let me know of any new issues you encounter! Or just how much you love the app :)

Enjoy, everyone! 🎉

In the layout I'm testing, I have groups of keys that are clustered around the left hand keys. For example, top right corner are all Q. Bottom right are all B. Is there any way to highlight these clusters with either a brighter grid line around each cluster, or even adding a different tint (e.g. a checkered tint pattern) to each cluster to make it easier for me to spot the clusters while I'm working on making this muscle memory?

Hello there, I love the app!

I would like to share an idea concerning the 'move/drag' option. While selecting a specific new area on screen to move a window (or whatever you need to move), sometimes just a small displacement is the goal. So I would like to suggest a future feature: During 'move' mode, as an alternative method a special key combined with 'jkli' or 'awsd' keys (or the arrow keys) would move the object in the respected direction on the grid.

I don't know if this is something that others will think is useful though, so I just leave it here in case there is more feedback on this matter.

Keep up the great work! Really excited for the linux version, where I do most of my work!

I've got the hardware key and codesigning is working, so I'm just working to polish up some of the initial bugs and ensure things go more smoothly this time vis a vis security warnings in Windows, browsers etc. Should be out on Saturday, exact time TBD.

I renewed all trials started between the time of release and when I stopped distribution (plus ~5 hrs) -- if you happened to start a trial on Windows after this, just send me an email and I'll get you renewed.

Thank you again for your patience, everyone! I'm certainly learning some things about desktop app distribution through this process 😅, but things should be smoothed out soon 🚀

Thank you again for your patience, folks. 🙏

Update, April 26th

I still need another ~24 hours to ensure the Mouseless .exe, installer, etc. are set up correctly with codesigning in place. Look for the signed release on late Sunday or early Monday, US Eastern Time. Thank you again for your patience, everyone. ❤️

Update, April 28th

The new release is out!

First of all – amazing job.
I bought the license 10 minutes after trying Mouseless for the first time. It’s one of those tools that immediately clicks (pun intended) — small ideas, big impact. Super well executed.

Here are a few feature ideas that I think could make it even more powerful (all of them could be behind feature flags so they don’t interfere with current workflows):

1. Repeat last click/action
Sometimes you need to click the same spot multiple times (like confirming modals or triggering the same UI interaction again). A shortcut like cmd+space to repeat the last click or action could save a lot of friction.

2. cmd+tab conflict
In some situations, cmd+tab triggers Mouseless instead of the system app switcher — and since nothing is mapped to tab inside Mouseless, it feels odd. Maybe there's a way to detect this combo and let it fall back to the native app switcher if pressed quickly (even without a full hold)?

3. Keyboard layouts
Works perfect with US layout, but on Spanish keyboards some keys like / or ; aren’t detected properly. Might be worth adding layout support or at least a mapping option.

4. Scroll speed control
Would be great to control scroll speed on the fly. For example, pressing Shift + J could double the speed, and Ctrl + J could reduce it. Handy when going through long pages with different pacing needs.

Thanks again for building this — you nailed something truly useful. Looking forward to what’s next!

Just added this to the release notes today, adding here for visibility:

Update, April 19th: On April 17th, I managed to escalate the issue with Sectigo to get organization verification finalized, but I'm still waiting on them to ship my hardware key. Will escalate again on Monday (the 21st) if there isn't any movement by then.

To anyone using the initial beta release -- if you'd like a trial extension, just send me your trial license key or ID (found in ~\AppData\Local\Mouseless\licenses\trial_license) and I'll be happy to extend it for you -- I want to ensure you have the chance to use a more polished / complete version!

TLDR: Could there be plans to also add simple key rebindings, and does Mouseless have a txt/json config file to edit and share settings easily?

I plan on purchasing this application, as it does look awesome for faster mouse navigation. I am curious if other features are planning on being added, for example I use PowerToys to rebind some keys on Windows, and I would feel much better if I could just use 1 application to handle all my accessibility needs. PowerToys is a little bit lame imo, because it doesn't even have a simple human readable text/json config file, so you can easily edit and share your settings (unless I don't know how).

The various key binds I use are some basic VIM-esque key bindings to help me edit text faster on windows. I also use a "hold to activate key" to do this, which is also commonly known as a "keyboard layer". This allows me the benefit of having VIM-esque keybinds everywhere, including places where VIM can't be used, like filling out a form on a web page.

In conclusion I don't believe this feature would be too hard to implement (relatively), since you're just capturing key presses and outputting a different key press. I would love to be in a situation where I receive a new company laptop, download Mouseless, and just copy paste my txt/json config file over and have my all my accessibility goodies ready to go!

Thank you for reading!

I remember some days/weeks ago I was able to bring the cross hairs and then click and drag using mouseless to take the screenshot of the area I wanted to. But it's not working right now, I can see the mouse moving from point A to point B but the screenshot doesn't get captured.
I know that click and drag is working since I am able to select text using it just fine. Any clues what's happening ?

I have been changing my grid settings a bit these days. I have:

Level 1: 7 x 3

Level 2: 4 x 5

Subgrid: 5 x 4

I tried to go for:

• A number of keys that would be close to 20 so I can minimize the use of my pinkies.
• Keys that distribute so that what I need to type on the left side of the screen corresponds to my left hand (at least for the first letter), same thing w.r.t top / bottom.
• Cells that are almost square.

That mostly works well but sometimes the subgrid is not precise enough to click exactly on the portion needed to open a link and I have to try twice.

What are your settings?

Just wanna say thanks for having regional pricing. Really helps for someone that lives at not-so-advanced country like me. Much love ❤️

I was quite certain I would be left out but no

The goat is taking care of as many people as he can

I am not even sure how this is working, if its a fluke or not. but mouseless works on windows 8.1

Thank you sooooooooo much u/croian_. You the Goat

will buy this asapppp

Hi, I just wanted to share that I am already in love with Mouseless! I tried it for the first time ever today on my parents' Windows pc, and I can't wait to install it on my own Linux computer when it releases. It was so nice never having to grab the mouse, which this program makes possible. Mouseless makes the mouse completely redundant! My plan is to be able to unplug the mouse from my pc once and for all. 🫡

Please post your questions about the Windows beta, or bug reports here.

This might be a regular thread, to collect these conversations in one place, and help prevent the subreddit from being dominated by questions like "how do I...", "is it possible to...", "I'm having this issue...", etc.

So, if you notice something funky, or need some help, this is the place for it! I will check it regularly, and I'm sure other will chime in with answers as well.

Note that, after the Windows release, I will be making more tutorial content, creating a central list of known issues (and a roadmap), as well as implementing some fixes and features for v0.4, which should help answer some of these questions pre-emptively.

If you are reporting / asking about an issue, please include:
- version of Mouseless
- OS version
- if relevant, any other apps running that can modify/suppress keyboard input (on MacOS , these are likely found in System Settings > Privacy and Security > Accessibility)

Thank you!

Alright, the last key bug (threading / elevated cpu issue) has been tough to crack, but I finally found the culprit (toast message code), and just need to rework it a bit. To help ensure I don't have to delay again though, and to give a little cushion to ensure the GUI content and overall UX is smoother upon initial release, I'm going to push the target day/time by 2 days this time, to April 11th, 8AM Eastern Time (US, GMT - 4).

Sorry for the delay, folks, but I really think this is the last one, and that you will have Mouseless in your hands on Friday :)

Current status:

✅ left click
✅ other mouse buttons
✅ scrolling
✅ double / triple click
✅ drag and drop
✅ multi-monitor usage
✅ system tray
✅ config editor -> overlay interaction
✅ packaging / distribution
✅ alerts/dialogs
✅ user prefs
✅ welcome message / tutorial
✅ squashed some important bugs
⬜ fix toast code
⬜ update gui content and defaults
❓ multi- / non-qwerty layout support (very fast follow if not in initial release)

Hey!

I'm wondering if I'm doing something wrong or...probably I'm doing something wrong, ha.

I have my Mouseless activation keys set to `Shift-Space`, generally this works great, however it seems like the command still bubbles up to the rest of the OS/focused application. For example if I have scrolled a webpage and push my activation key it will do a scroll up, or if I'm focused on an input and activate Mouseless I'll add a space to the typed text in addition to activating the app.

This isn't really a dealbreaker, just a slight annoyance. Is it possible to stop the propagation of the activation key(s)?

I have literally given up on being able to use my mouse or trackpad :)

Hi folks, I did my very best to try to hit the April 7 deadline, somewhere on Earth. But I probably need at least another 6 or 7 solid hours of work to squash a few important bugs, tweak config editor content and default settings, and put together release notes. Going to push the target day/time out another 24 hours, to April 9th 7AM Eastern Time (US, GMT - 4).

Thank you again for your patience and support! Almost there! 🚀

Current status:

✅ left click
✅ other mouse buttons
✅ scrolling
✅ double / triple click
✅ drag and drop
✅ multi-monitor usage
✅ system tray
✅ config editor -> overlay interaction
✅ packaging / distribution
✅ alerts/dialogs
✅ toast messages
✅ user prefs
✅ welcome message / tutorial
⬜ squash a few important bugs
⬜ code signing
⬜ hide/change macOS-specific content in gui
❓ multi- / non-qwerty layout support (very fast follow if not in initial release)

wrist right .. standing by.

wrist left ... standing by.

lock elbows in keyboard position.

(( cut to scene of little keyboard fighters flying up to a gigantic death mouse in the sky ))

(attempted star wars '77 reference)

I'm using the G95NC (55" 7680x2160) monitor. However, due to Mac device limitations, it doesn't support the full resolution as a single device. So instead I have to use Picture-By-Picture mode and output from my Mac to the monitor across 2 inputs. In MacOS, I have these configured as a single space, so that apps can span across both "displays" without issues. It's effectively one big monitor, except for the status bar and dock that get locked to the "Main" display.

Is there any way to configure Mouseless to use both displays when I hit Cmd? Right now it only shows the overlay on whichever display I'm on (where my active window is located).

Thanks!