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

How to find files by what they contain and open them on another screen with Atticus Mac

Ask Atticus for a file by its topic and it searches inside your files and opens the match.

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

Who it is forA person with a lot of notes, documents or saved research who remembers what a file says but not its name.

The problemSearching by file name misses notes you wrote months ago, and digging through folders wastes time.

The outcomeYou say what the file is about and Atticus finds it by its contents and opens it on your other screen.

What you need first

  • A Mac
  • A Claude Pro or Max plan, or a local model server such as Ollama, LM Studio, llama.cpp or vLLM
  • Claude Code installed (needed for the local model setup; the README says it does not require a Claude account in that case)
  • Permission for Atticus to use the microphone and Accessibility controls

Steps

  1. Open Atticus and hold ⌃ control, ⌥ option and space.
  2. Say what the file is about, for example: "Find my notes about the Tokyo trip."
  3. Check that the match opens on your other screen.
  4. If the wrong file opens, say a correction, then say "remember" followed by the rule so Atticus saves it for next time.

Prompt for your agent

Using the repo SaarthurR/atticus-mac, ask Atticus to find files about <topic> by their contents. Expected output: the best matching file opens on the other display. Verify that the opened file contains the topic named in the request.

Caveat. Atticus reads your files and screen, so it works only on what your Mac already gives it access to, and it asks before deleting, sending or changing files.

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