Show HN: Ownscribe – local meeting transcription, summarization and search
Show HN (score: 5)Description
As someone who hates taking notes, but also forgets things easily, I found the idea of transcribing and summarizing meetings automatically neat. However, all the existing tools out there store everything on their servers, don't work with every type of meeting, and cost $30/month or more.
I wanted a tool that just runs locally and uses a very simple format (like .md) to integrate with my other workflows – but there wasn't anything like that. That's why I started to build ownscribe over the past few months and continuously improved it. It started as just a tool for transcription and summarization, and now even allows you to search past meetings with natural language (and a local LLM).
At the moment, it is mainly optimised for macOS (although Linux should also partially work). I'd love to have some more feedback on how to make it more useful!
More from Show
Show HN: Ccgs – Collaborative Claude Code sessions, stored in Git branches
Show HN: Ccgs – Collaborative Claude Code sessions, stored in Git branches My team uses Claude Code daily, and the sessions have become some of the most useful artifacts we produce. But they're trapped in ~/.claude/projects/ on whichever laptop they happened on. There's no good way to hand a colleague "the session where I untangled the migration" so they can claude --resume it and keep going from where I left off. Enter ccgs: Share Claude Code sessions through an orphan branch (@ccgs/<name>) in your existing repo's remote<p>- Session files carry the author's absolute paths. On pull, ccgs rewrites the working dir back to your path so resume actually works — surgically editing only the structural cwd field, not a blind find-and-replace that would happily corrupt the transcript.<p>- Everything goes through git plumbing (hash-object/commit-tree/update-ref) against a throwaway index. It never touches your working tree, index, or current branch, and it's fine with a dirty tree. It will not git checkout something behind your back.<p>To try it without installing: `npx claude-git-sessions`. This also incidentally allows you to move a directory and carry the claude code transcripts with it (just push first, then move the directory, then pull)<p>IMPORTANT CAVEAT: Unless you have a very good security hygiene, your Claude Code sessions are likely full of sensitive information such as environment secrets. Use with caution and avoid using on public repositories. Branches used by ccgs are prefixed by `@ccgs/` so you can easily filter them out.<p><i>This project was written by and with Claude Code. This Show HN was not.</i><p>(Reposted with URL fixed)
No other tools from this source yet.