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

How to add a custom URL lookup action to the popup with Openclip

Create an extension folder with one Openclip.json file that sends selected text to a search URL.

Who it is forA researcher or analyst who looks up selected terms on the same reference site over and over.

The problemLooking up each selected term on a reference site means copying it, opening a browser, and pasting it into the search box.

The outcomeA Lookup action appears in the popup and opens the reference site search for the selected text.

What you need first

  • A Mac running macOS 14 or later
  • Accessibility permission granted to OpenClip
  • Homebrew for the recommended install

Steps

  1. Run mkdir -p ~/.openclip/extensions/com.example.lookup to create the extension folder. (inferred, check the README)
  2. Create openclip.json in that folder with an identifier, a name, and an actions list.
  3. Give the action "type": "url" and a url value that contains {query}.
  4. Select text in any app and choose the new Lookup action from the contextual bar.

Prompt for your agent

In the OpenClip repo at https://github.com/ganeshmshetty/openclip, create ~/.openclip/extensions/<identifier>/openclip.json with one url action whose url contains {query}. Expected output: the file exists and is valid JSON, and the action appears in the popup for selected text. Verify the JSON parses before testing it in the popup.

Caveat. The README shows the format only for a URL action, so shell, JavaScript, or AppleScript extensions need the developer guide linked from the README.

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