Talk to your Mac.
Watch it work.
Rovyk lives in the notch and operates your machine. Apps, files, mail, calendar and the web. It hears, thinks and speaks on-device.
Where can I be?
Two surfaces, one agent. Switch mid-sentence, it keeps the thread.
Hands free, in the menu bar
Say the wake word. It drops open, works, then retracts.
A window, when talking is not an option
Unpin the notch and type instead. Same brain, same gate.
Both surfaces, one 84 MB download
Apple Silicon, macOS 27 or later. No account, no sign-up, nothing to configure.
10 groups. 59 tools.
Sweep the spectrum to see what any one of them reaches, and what it has to ask you for first.
send_mail
Sends it. This is the step the gate stands in front of.
Say it once. Watch the whole chain run.
No command list, no scripts to wire up. One sentence, and Rovyk decides what to call, asks before anything irreversible, then tells you what it did.
Five states. You always know which one.
Awake. Not listening.
Nothing is captured until the wake word lands.
- Geometry
- Globe
- Why
- Always-on local detector
Hearing you, on your machine.
Speech to text runs on-device. Your voice never leaves the Mac.
- Geometry
- Wave
- Why
- Zero audio crosses the network
One brain. Fifty-nine tools.
It reads the request, the thread and the screen, then decides.
- Geometry
- Rubik
- Why
- No routing table, no fixed intents
Doing the actual thing.
Apps, files, buttons in software that never heard of Rovyk.
- Geometry
- Orbits
- Why
- Clicks via the Accessibility API
Answering out loud.
A bundled on-device voice. Your hands stay where they were.
- Geometry
- Ribbon
- Why
- Supertonic TTS, shipped inside
Built for how you actually use a Mac
Three things no other assistant on this machine will do for you.
It works with apps nobody integrated
Other assistants only reach software they have partnered with. Rovyk drives the macOS Accessibility API, so it operates any window the way you do: click that button, type in that field. If you can do it with a mouse, you can ask for it.
It keeps working while you do
Start something that takes minutes and carry on. Task chips fill in, progress is spoken, and checkpoints let you correct it mid-run instead of finding out afterwards.
It remembers across sessions
Which folder your invoices live in, how you like replies worded, what the project is called. Ask what it can do and it answers from live connection state, not a canned script.
Why you can hand it the keys to your Mac
It is unsandboxed, it clicks real buttons and it touches real files. Three mechanisms sit between that power and your machine.
It asks before anything irreversible
- Enforced by
- code, not the model
- Stands in front of
- delete · move · send
- Default answer
- cancel
Try it. Cancel actually cancels.
Move 47 files from Downloads to Archive?
invoice-q3-final.pdf
screenshot-2026-08-04.png
+ 45 more
Nothing has moved yet.
It cannot lie about what it did
- Runs
- after every reply
- Compares
- claims against what ran
- On a mismatch
- the reply is corrected
Every reply is checked against what actually ran.
Caught before it reached you. Reply corrected.
You grant access one piece at a time
- Granted
- one at a time
- Revoked in
- System Settings
- Without any of it
- it still runs
Turn any of it off and it keeps working without that piece.
no app control
What it needs. What it will not do.
Published in full, because a tool asking for this much access should tell you exactly where it stops.
Apple Silicon
M1 or later
Intel Macs are not supported.
macOS 27
or later
A menu bar utility, not a windowed app.
8 GB
16 GB recommended
To run local models well.
What needs a key, and what doesn’t.
- System control
- Files
- Mail and calendar
Reasoning still runs on-device, and is measurably weaker on complex, multi-step work.
- Web browsing
- Web search
- The strongest reasoning
Your provider, your key, your bill. Nothing is billed through us, and none of it is on by default.
Everything you need to know
Sandboxing would remove the product. An App Store app cannot drive other applications through the Accessibility API, reach folders outside its container, or run a background agent the way Rovyk does. We ship a direct download instead, so the capability survives.
By default, nothing. Speech to text, the model and the voice all run locally. If you add a cloud API key, the text of that specific request goes to the provider you chose, on your account. There is no Rovyk server in either path.
That permission is what lets it click buttons and type into apps that have no integration. It is the difference between an assistant that describes what to do and one that does it. You can revoke it in System Settings and everything else keeps working.
Only after you say yes. Deleting and moving both sit behind a confirmation gate written in code, independently of the model. It also only ever sees the folders you explicitly granted.
It runs fully offline on a local model. System control, files, mail and calendar all work. Web browsing and web search are unavailable, and long multi-step reasoning is noticeably weaker than with a cloud model.
No. Rovyk is Apple Silicon only, M1 or later, on macOS 27 or later. The local models and the bundled browser agent both depend on it.
Say it once.
Your Mac has been waiting for a better interface than the mouse.