How to use Claude to organise voice transcripts
The author used Claude Code to structure exported voice transcripts, extract decisions and build a searchable knowledge base plus a portable CLAUDE.md file.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Process [voice transcript export] locally. Organise records by date and topic, extract supported decisions, action items and insights, and build a searchable cross-referenced knowledge base. Generate [CLAUDE.md path] covering working style, preferences and ongoing projects using only transcript evidence.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- joozio
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports a local searchable knowledge base and a CLAUDE.md file that gives assistants personal context without the entire conversation history.
- Human involvement
- The post does not describe review steps for extracted decisions or personal context; the author reports building and sharing the workflow.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Parsed and structured transcripts by date and topic.
- Extracted decisions, action items and key insights.
- Built a searchable knowledge base with cross-references.
The author had worn a Limitless Pendant for six months, accumulating roughly 10GB of recorded conversations. They report needing to export that material within 30 days before deletion after the device was banned in the EU. The post describes a mismatch between the device's memory promise and a transcript collection too large to fit into an LLM context window.
To make the exported material usable, the author built a local workflow with Claude Code. It first parses and structures transcripts by date and topic. It then extracts decisions, action items and key insights, before building a searchable knowledge base with cross-references. The final stage generates a CLAUDE.md file containing portable personal context.
That file describes the author, their working style, preferences and ongoing projects. The author says an AI assistant can read it for context without needing the entire conversation history. They also say they wrote up the full prompts for others using voice exports, including Omi or Plaud data, although those prompts are not reproduced in the supplied text. The reported result is a local knowledge workflow and reusable context file.
Who it's for: People with large voice-transcript archives who want searchable records and concise assistant context.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · joozio
Frequently asked questions
What does the workflow extract?
It extracts decisions, action items and key insights after parsing transcripts by date and topic, then builds a cross-referenced searchable knowledge base.
What goes into the CLAUDE.md file?
The author describes a structured file covering who they are, how they work, their preferences and ongoing projects.
More details
Remaining steps
- Generated a CLAUDE.md file with portable personal context.
About this account
Claude Code supported a local workflow that transforms transcript exports into structured knowledge and portable assistant context.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=46705214. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: joozio on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Limitless Pendant exports · CLAUDE.md
Voice transcripts · Personal knowledge
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.