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

How to keep minutes local for meetings that cannot leave the room with Meetcap

Transcribe and write minutes on your own computer with MeetCap's local model, with no key or account.

Who it is forA manager or advisor in a confidential meeting whose content must not be sent to any outside service.

The problemCloud AI tools would send the meeting text to a provider, which is not allowed for some meetings.

The outcomeYou get a transcript and minutes that stay on your computer, exported as Word or PDF if you need to share them.

What you need first

  • A Mac with macOS 14.2 or later, Apple silicon or Intel
  • Permissions granted during MeetCap setup (covered in the docs at meetcap.seacen.dev)
  • An AI agent such as Claude Code or Codex for agent-driven use cases, or a local model, your own API key, or a compatible agent for minutes

Steps

  1. Download MeetCap from https://meetcap.seacen.dev/download, open it and follow the setup.
  2. Choose MeetCap's local model when you are asked which AI writes your summaries and minutes, so MeetCap downloads and sets it up on your computer.
  3. Start the recording from the menu bar before the meeting, and let it run offline.
  4. When the meeting ends, open the minutes, fix any flagged or misheard names, and confirm the speakers.
  5. Export the minutes to Word or PDF only if the recipients are allowed to receive them.

Prompt for your agent

Using the seacen/meetcap repository, set MeetCap to its local model and record the meeting <meeting name>. Expected output: a transcript and minutes saved on this computer. Verify that no network request carries meeting text by checking the setting shows the local model is selected.

Caveat. The README says the local model keeps even the text on your computer, but the model and speaker recognition details are only in the docs, so check them before relying on this for confidential work.

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