QUICK ANSWER
Give your agent a useful video and ask it to save the context with Clipy. Later, ask about the idea you want to use. Your own screen recordings work the same way: show a process, explain a decision, or walk through a solution, then keep that context available for the next task.
Save this video with Clipy so we can use its explanation when working on this project: [link].
Two things called "knowledge base"
Search for "build knowledge base from youtube videos" and you get two completely different articles wearing the same title.
The first is B2B: you run a support desk, you have help articles, and you want to embed videos in them or generate articles from your product's YouTube channel. That is a documentation product problem, and tools like Docsie and CustomGPT are built for it.
The second is personal, and it is the one nobody has solved well: you watch a lot of video, almost none of it sticks, and six weeks later you remember that somebody explained the thing but not who or where. The video is in your watch history, or a bookmark folder, or a "Watch Later" playlist with four hundred items in it. Functionally, it is gone.
This article is about the second one. If you are here for the support-desk version, none of the following will help you.
Why the bookmark folder fails, precisely
It is worth being specific about the failure, because the specifics dictate the fix.
A bookmark stores a location, not content. You cannot search it. "Which video mentioned the retry backoff" is unanswerable against a list of titles, because titles are marketing and the substance is forty minutes in.
Re-watching does not scale. Even if you correctly guess which of five candidate videos holds the answer, finding the moment inside a fifty-minute talk means scrubbing. Chapter markers help when creators bother, which is sometimes.
It rots. Videos get unlisted, deleted, or region-locked. A pointer to someone else's content is a pointer that can be revoked, and you find out at the worst moment.
Nothing else can read it. This is the one that changed recently. If you work with a coding agent, everything else in your working life is machine-readable, your repo, your docs, your issues, your notes. Your video is not. The knowledge you specifically acquired by watching something is the one category your agent cannot reach, which means you become the manual bridge, re-explaining from memory what you half-remember.
The part most tools get wrong: the visual half
Nearly every "save YouTube to notes" tool works the same way: pull the caption track, summarize it, write it somewhere. Snipo, Tube2Note, Glasp, Eightify, the Obsidian plugins, and NotebookLM all land in that family. Google's help centre states the behaviour for its own product in one flat sentence"Only the text transcript of the video is imported as a source" (Gemini Notebook Help, the product formerly and still widely called NotebookLM).
For a panel discussion or an interview, that loses almost nothing. The substance genuinely is the words.
For a tutorial, it loses the point. Watch any competent screen-recorded walkthrough with the audio muted and you will see how much information is carried by the picture: the file path in the sidebar, the flag in the command, the exact error text, the version in the corner, the shape of the config. Now do the inverse, read the transcript with the video closed, and you get sentences like "and then we just add the middleware here." Here is doing enormous work in that sentence, and the transcript does not contain here.
We ran a lot of developer-oriented video through both paths while building this, and the pattern was consistent enough to design around: the more useful a video is to somebody trying to do the thing, the more of its information is dictated by the screen rather than by the speaker. It is easy to check against your own sources: mute one and see what survives.
So the first requirement for a video knowledge base worth building is that capture has to keep the visual evidence, at least where the visual evidence is load-bearing.
How do you build the library with your agent?
Start with the recording link and the task. If the agent needs the Clipy skill or account access, ask it to handle setup and guide you through anything it needs. You can keep explaining what you want in ordinary language.
Use Clipy to save these tutorials to my library under “Reference.” For each one, keep the useful context and tell me what evidence is missing: [video links].
Start with a few videos you actually expect to reuse. Let the agent import and organize the material. Connect your account if needed, and ask it to confirm which items were saved.
How do you find something later?
Find the recording where we discussed the retry policy. Explain the decision and link to the relevant evidence.
Searchable context is more useful than a folder of bookmarks because the agent can work from what was said and shown. It should still identify gaps when a transcript or frame could not be captured.
Can you include local videos?
Yes. Give the agent access to the authorized video file and ask it to add that material with Clipy. If it needs a transcript or another prerequisite, it should explain that before claiming the import is complete.
Reading the sufficiency report, and why it exists
Every bundle carries a report in manifest.json that answers one question: how much of this video does the document actually contain? It names the timestamps where the transcript goes blind, the moments where the speaker referred to something on screen that the words do not describe.
This sounds like a small feature and it is the one worth understanding, because it is the difference between a document that lies to you and one that does not. Every transcript-only tool produces output that reads complete. There is no visual signal in a wall of well-formed prose that says "a quarter of the information in this video is missing." The reader, you, or worse, an agent that will act on it, has no way to know it is working from a partial record.
An agent reading a Clipy document sees the gaps declared up front, in the header, before the transcript starts. That changes its behaviour in the way you want: it can say "the transcript references a config file at 12:40 but does not show it" instead of confidently inventing what was probably in the file. Hallucination in this setting is usually not a model failing so much as a document that presented itself as complete when it was not.
The same header carries an untrusted-content warning, which matters more than it sounds. A video transcript is text written by a stranger, and an agent that reads it should treat instructions inside it as data rather than as instructions. Marking that boundary explicitly is cheap and the alternative is unpleasant.
Curation is the part that decides whether this works
A knowledge base that grows without pruning becomes the bookmark folder again, just with better search. Two habits keep it useful.
Save useful context while the video is fresh in your mind. Tell the agent which topic or folder it belongs in, and ask it to confirm what it saved. A clear name now makes the material easier to find later.
Import less than you watch. The instinct is to capture everything, and it is wrong. Signal-to-noise in search is the whole value; a library of forty things you deliberately kept answers questions better than a library of four hundred you passively hoovered up, because in the second one every query returns twelve results and you are back to guessing. The filter to apply is simple: would I plausibly go back to this? Most videos, honestly, no.
The corollary is that this is not a "save everything automatically" system and is not trying to be. It is closer to a reference shelf than a hard drive.
How this compares to the manual alternatives
Bookmarks and Watch Later
Free, instant, and they do not work, for the four reasons at the top of this article. Worth saying plainly because most people's actual system is this one, and the honest comparison is not against some other tool, it is against doing nothing.
Clipping to Notion or Obsidian
The Snipo / Tube2Note / NotionSync family, and on the Obsidian side a set of transcript-fetcher plugins. They are quick to set up if you already live in one of those apps.
Two structural limits. The output is a note, the endpoint is a page in your vault, and nothing indexes across what you saved beyond that app's own text search, which does not know a transcript from a grocery list. And they are transcript-shaped, so the visual half is gone (Snipo's manual screenshots being the partial exception, and manual is the operative word). Obsidian keeps plain files an agent can grep, but grep over transcripts still misses everything that was shown on screen.
NotebookLM / Gemini Notebook
NotebookLM is free and needs no setup, with a chat interface that cites its sources.
Its limits for this job come down to documented behaviour rather than opinion. Its help centre records that only public videos with existing captions can be imported, that videos without speech are unsupported, that only the text transcript comes in, and that a source is auto-deleted within 30 days if the video is deleted or made private (source). Google's FAQ documents the allowance as 100 notebooks with up to 50 sources each (source).
Put together, that describes a notebook: a bounded, curated project you build for a purpose. It is not an unbounded personal memory of everything you have watched, and the 30-day rule means what is in it is not entirely yours. If you want the full breakdown of those limits we wrote one up in NotebookLM and YouTube: every documented limit.
AI summarizer extensions
Eightify, Glasp and the rest give you a summary in the sidebar while you watch. Useful for triage, should I watch this at all, and close to useless as memory, because a summary is lossy by construction and the thing you will need in six weeks is the detail the summary dropped.
How you use it
It is an agent-driven workflow. You give the agent the video and your request, and it handles the Clipy steps. Ask it explicitly when you want material saved for later, so your library stays deliberate.
Clipy then works as your searchable video memory: hybrid search across your recordings and imported videos, ask-the-video Q&A, and cited moments your coding agent can retrieve during a task. Give it a question, and ask it to cite the moments that support its answer.
Knowledge-base search is included on every plan: imported YouTube, Loom and local videos sit next to your own recordings, and search finds them by meaning as well as exact words. It is one of several tools Clipy includes beyond recording, alongside screenshots with an 18-tool markup editor, clipboard history in the Mac and Windows apps and free video tools.
What is a useful first experiment?
Add these three videos to my Clipy library, then answer this question using them: [links and question].
Check the answer against the cited moments. Keep sources you expect to use again and remove the ones that do not help. The agent handles the mechanics; you decide what belongs in your library.