One shortcut, then a loop.
There is no second window to learn and no dashboard to live in. Cursorly runs in the tray, and everything happens inside whatever app you were already in.
Signed installer.
The loop.
- Press the shortcut. Ctrl + Win + Alt + K by default, changeable. It fires from inside any app, and from the desktop.
- Say what you want. A sentence, like "get this into a PDF" or "turn off the notification sound." You are describing an outcome rather than naming a command.
- It takes in the screen. What is open, what is on it, and what state that is in. No picture of it is taken at any point.
- It works out a route. From where you are now to the thing you asked for, as a sequence of places to go next.
- It points at the first one. A second cursor glides there and holds. Your real cursor is untouched.
- You act, and it looks again. Every change to the screen restarts the loop from the new state, so a dialog you did not expect is the next step rather than a broken script.
If a step needs text typed, it shows you the exact text. You type it.
Why it keeps looking.
Anything that memorises a path breaks the moment something moves: a different window size, a version update, a dialog that shows up on some machines and not others. Cursorly does not memorise a path. It works from the screen in front of it and decides again at every step, which is slower to explain and considerably harder to break.
Where it lives.
In the tray
It sits in the system tray and does nothing until the shortcut. There is a dashboard for history, usage and settings, but you never have to open it.
Not watching
It wakes when you ask and stops when the task ends. No background observation, and no screenshots at any point.
Signed and self-updating
The installer is signed, and updates arrive quietly. What each release changed is on the changelog.
We're new.
It gets things wrong sometimes. Tell us when it does.