Make years of calls, podcasts and posts searchable with Claude Code

Posted

Feb 11, 2026 by Andre Haykal Jr (@andrehaykaljr)

·

Last checked

Oct 16, 2026

·

Method:

How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Outcome

Claude Code organized years of calls, podcasts, tweets and presentations into a searchable database connected to AI, with a daily job that adds new content; asked for a masterclass outline, it drew on 224 chunks from 78 sources.

Agent

Claude Code

The source didn't share its exact prompt, so we wrote this from what it describes.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Gather all my past content into one searchable library I can ask questions of, and keep it updated.

Check with me first: Where does my content live (calls, podcasts, posts, slides)?

What I'll give you:
- My content files or exports
- Where new content shows up each day

Rules:
- Organize everything with its source and date.
- When answering, cite which pieces of content you used.
- If something is missing or unclear, ask me instead of guessing.
- Keep the library private.

Output: A searchable library plus a daily update, and answers that cite their sources.

You'll know it worked when: I can ask a question and get an answer built from my own words, with sources.

Later I may also ask you to: draft new material, like a masterclass outline, from my past content.

Here's a task I'd like your help with. Read it all the way through before you start.

Goal: Gather all my past content into one searchable library I can query, kept up to date.

Quick check first: tell me if anything below is missing or unclear.

Inputs (fill in or confirm):
- Content sources
- Where new content arrives
- Search tool preference
- Privacy limits (what must stay private)

Rules:
- Keep source and date for each item.
- Chunk and index content.
- Set up an update routine.
- Answer with citations.
- Make each search result show the source, date and a link to the original.
- Avoid duplicates when the same content appears in several places.
- Log each update run.
- Tag each item with source, date and type.
- Keep private items out of shared indexes.
- Test with five real questions.
- Make the update job rerunnable without duplicates.

If you get stuck: If a source can't be exported, note it. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords.

Verify before you finish: Test with 5 questions.

Output: Library and update script.

Done when: I can search and get cited answers.

Source

https://x.com/andrehaykaljr/status/2021676546218434695