DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find out why a run failed and replay it offline with Typesafe Computer Use

Inspect one screen with clicker-inspect, then replay a saved run folder without a live screen.

Authorization notice. Typesafe Computer Use is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer or power user whose agent run stalled or chose the wrong action and who needs to see what it read.

The problemA wrong click on a live screen is hard to explain after the fact, and reruns can change the outcome.

The outcomeYou see the annotated screen and payload for one capture, and you can step through a saved run folder to find the failing decision.

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

  1. Complete the install steps in the repo
  2. Run uv run clicker-inspect "<goal>" to capture the screen after a 3-2-1 countdown (inferred, check the README)
  3. Open the annotated screen and payload that the command produces
  4. Locate the run folder under runs/ for the failed run and follow docs/run-folder.md to replay it offline
  5. Attach the run folder to a bug report, as the CONTRIBUTING notes ask

Prompt for your agent

In the typesafe-computer-use repo, run `uv run clicker-inspect "<goal>"` and then open the saved run folder for the failed run under runs/. Report which action was chosen, what the OCR and accessibility tree showed, and where the decision went wrong. Verify that the annotated screen and payload were produced before drawing any conclusion.

Caveat. The README says to clear the terminal first because its text is on screen and would be read as OCR input, so the capture can be polluted if you skip that step.

Share: 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