Authorization notice. Typesafe Computer Use is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Credentials. The README's login example and the optional CLICKER_EMAIL variable mean the agent may type account details, so keep credentials in your local .env file only.
Who it is forA Mac user with a repetitive click-through task in Chrome, such as reaching a page after several menus.
The problemRepeating the same series of clicks across several pages takes time, and frontier-model computer use is slow and costly for each step.
The outcomeThe agent works toward the goal, stops on done, low confidence, a stall, or the step limit, and prints an answer when the writer is used.
What you need first
- A Mac running macOS 14 or newer
- Python 3.12 or newer and uv
- A TypeSafe API key for TYPESAFE_API_KEY
- Screen Recording and Accessibility permissions granted to your terminal
- Optional: an Anthropic API key for type_text, writer-proposed URLs, and the final answer
Steps
- Complete the install steps and grant Screen Recording and Accessibility
- Clear the terminal so its text is not read as OCR input
- Run
uv run clicker "<goal>" --act --steps 20 --delay 3for a slower, bounded run (inferred, check the README) - Press Ctrl-C or move the mouse into the top-left corner to stop a live run
- Read the printed answer, and open the run folder under runs/ if the result is wrong
Prompt for your agent
In the typesafe-computer-use repo, run `uv run clicker "<goal>" --act --steps 20 --delay 3` and report the final answer and the stop reason. Verify that the run folder was written under runs/ and that the stop reason is one of done, low confidence, a stall, or the step limit.
Caveat. The README warns that settings and behavior change between 0.x releases and that the loop can still have rough edges.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page