JevMade field notes / Written guide

Control macOS through named interface controls

macos-computer-use-kit lets AI software read and operate macOS controls through commands. It favors named buttons, fields, menus, and windows over guessed screen coordinates and can send input without taking over the user's pointer.

Original by Sur-CaiBrowser use

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“macos-computer-use-kit” by Sur-Cai. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 Sur-Cai

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

The kit reads controls identified by names and roles, such as a Send button or search field, instead of relying only on screen coordinates. It can operate macOS applications through a command line while leaving the user's pointer alone.

The assistant reads available controls, chooses one, performs an allowed action, and checks the result. Local rules require confirmation before actions such as sending or deleting. The optional Jev check is the kit's only network feature: using it sends supplied task and interface context to TypeSafe.

macOS requires Accessibility permission, allowing software to inspect and operate interface controls. Some apps expose little useful information. Review what an optional online check will send, and keep fixed permissions, confirmation, and result checks: a model's judgment does not authorize an action.

Key takeaways

Prefer controls identified by names and roles to fragile screen coordinates.
Verify the application state after every action.
Keep rules for actions that cannot be undone in the local program.

More guides →See the experiments →