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

How to check what an app window shows after each step with macOS Harness

Read a window, act once, then read again to see only what changed.

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

Who it is forA QA tester or support engineer who needs to confirm how a Mac app responds to a sequence of actions.

The problemChecking each step of a Mac app workflow by hand is slow and easy to skip.

The outcomeA short log of each action and the changed window text after it, so the tester can see what the app did.

What you need first

  • A Mac running macOS, since the project is macOS only
  • Python 3.12 and uv, to install macOS Harness
  • Accessibility and Screen Recording permissions, which every call needs
  • A coding agent CLI such as Claude Code or Codex to run the commands

Steps

  1. Install macOS Harness with uv using Python 3.12, then run macos-harness install --agent codex or your agent's name. (inferred, check the README)
  2. Run macos-harness get_app_state --app "TextEdit" to record the starting window.
  3. Run macos-harness press_key --app "TextEdit" --key "super+s" to trigger the action under test.
  4. Run macos-harness get_app_state --app "TextEdit" again and compare it with the starting read.
  5. Run macos-harness telemetry disable if you do not want anonymous telemetry on this machine.

Prompt for your agent

Using the macos-harness repo at https://github.com/browser-use/macos-harness, read <app name> with `macos-harness get_app_state`, perform the action in <test steps>, and read the window again. Verify and report only the lines that changed between the two reads, and state whether the expected change appeared.

Caveat. The change report depends on the accessibility tree the app exposes, and Electron or plain web view apps give no URL to check.

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