Every product in the AI second brain category launched in the last year has gotten excellent at the same problem: catching things before you forget them. Almost none of them have shipped anything for the problem that shows up six months later, which is figuring out which of the thousand things you caught is worth surfacing right now and whether it is still true.
If you are building here, that gap is worth looking at directly, because it is where the next real product sits.
What the capture side actually looks like now
Genspark's SecondBrain Note, which launched in July, is a good marker for how far capture has come. It is a 2.95mm-thin, 26g hardware recorder that clips to a phone, runs a four-microphone array, holds 35 hours of battery, and stores up to 64GB of audio locally, all for $179 at launch. It listens to meetings and calls and turns them into notes and follow-up actions automatically. Genspark's own framing, from co-founder Eric Jing, is that using AI today is like working with a genius who has a goldfish memory. Fair pitch. But notice what the product actually does: it captures more, faster, with less friction. It does not address what happens to that audio a month later.
That is not a knock on the product. Capture used to be genuinely challenging, and now it basically is not. A recorder that fits on a phone and transcribes a week of conversations before you open an app is a solved engineering problem, executed well. The opportunity has moved past it.
The thread that shows the real fault line
A Hacker News post this week, "It's so hard to finish an idea that is not yours and is just suggested by AI" (213 points, 115 comments as of this writing, linking to an essay called "Keep AI Out of Your (Obsidian) Vault"), is a rare case of this space producing a genuinely substantive argument instead of tool-comparison bait. The core complaint from commenters was not that AI-assisted notes are unhelpful. It is that once an AI-generated note sits next to your thinking without a clear source trail, you lose the ability to tell your judgment from a plausible-sounding suggestion.
That complaint has research behind it now, not just anecdote. A CHI 2026 study from the University of Bayreuth and Aalto University had 184 participants generate ideas both with and without an AI chatbot, then tested their memory of the source a week later. When people reworded an idea themselves, they correctly recalled it as AI-generated only 37.7 percent of the time. Mixed human-AI workflows, which is most of how people actually use these tools, produced the steepest errors of any condition tested. In plain terms: users cannot reliably tell you, a week out, which of their own notes came from a model and which came from them. Assuming they will remember to disclose that, or curate around it, is not a realistic product assumption.
What this means if you are building
The obvious move is source tagging at the moment of capture, not reconstruction after the fact, which is what the Bayreuth researchers themselves recommend. But the harder and more interesting problem sitting underneath it is staleness with confidence: a note that was true in March and is still indexed, still tagged, and still surfaces with exactly the same confidence in August, even though the thing it describes has since changed. Nobody in this category is shipping for that yet. Most retrieval still relies on similarity search over a pile of data that has no sense of its own shelf life.
If your product only makes capture easier, you are shipping the half of this problem that is already commoditized. The harder, still-open half is retrieval that knows when to doubt itself and provenance that survives longer than the user's memory does.
What would you actually want a note-taking or memory tool to do differently here—like automatically tagging sources, expiring low-confidence notes, or something else entirely?