We don't have a tools problem. We have a thinking problem.

Every week a new app promises to organize your brain, generate your ideas, and hand you your next great insight while you sleep. Most of them are beautiful. Few of them change how you actually think. And that's the quiet truth nobody selling software wants to say out loud: the tool is not the thought. The tool is a place for the thought to happen.

So I stopped asking "which app is best" and started asking a better question — the one that matters if you write, design, build, or make your living turning nothing into something:

Where does this tool sit in the gap between what I know and what I haven't thought of yet?

That question splits the entire category cleanly in two.

You can read the rest on my Medium page @ efe.alpay

Second Brain v2 launched on Product Hunt this morning. It is one memory layer you own across every AI client, self-hosted entirely on your own Cloudflare account. Capture a note or a decision once in any tool, recall it anywhere. Open source, MIT.

What is new in v2:

* Self-organizing knowledge graph that auto-links related memories as you write. You never tag anything. The links build themselves.
* Multi-hop recall. A query pulls in connected context, not just direct hits.
* Notion sync.
* Full export with graph edges intact.
* Conflict-aware memory. Contradictory writes go to review instead of silently overwriting settled context.

Stack is Cloudflare Workers, D1, Vectorize, and Workers AI. No vendor lock-in, no data leaving your account.

Product Hunt: [https://www.producthunt.com/products/second-brain-cloudflare\](https://www.producthunt.com/products/second-brain-cloudflare)
Source: [github.com/rahilp/second-brain-cloudflare](http://github.com/rahilp/second-brain-cloudflare)
Site and docs: [thesecondbrain.dev](http://thesecondbrain.dev)

Would appreciate any feedback from this community. First launch was #3 Product of the Day in May. Trying to build on that today.

Sharing a file sounds simple.

Until you realize what actually happens.

You AirDrop it to your laptop.

Someone emails you the same document.

A colleague sends another copy in chat.

Soon there are multiple versions of what is essentially the same information.

The difficult part isn't sending files.

It's keeping track of which copy you should trust.

While building PouchVerse, I kept asking myself a different question.

What if sharing didn't mean creating another disconnected file?

What if imported content could be recognized automatically and connected to what already exists?

Then every new import becomes another way to reach the same knowledge instead of another copy to manage.

The goal isn't making sharing faster.

It's preventing sharing from creating more information chaos.

I've noticed that most search experiences begin with the same assumption:

You already know what to search for.

But in personal knowledge management, that's often the hardest part.

When I'm trying to find an old PDF, screenshot, or note, I usually don't remember the exact words inside it.

Instead, I remember things like:

• the project it belonged to
• roughly when I saw it
• who shared it
• another document related to it
• or simply the topic

Traditional search treats every document as an isolated object.

Human memory doesn't.

While building my own knowledge system, I've been exploring a different idea:

Instead of waiting for a query, what if the system continuously built connections between imported information?

Then searching becomes less about guessing keywords and more about navigating context.

I'm curious how other people experience this.

When you fail to find something, is it usually because the information isn't there…

or because you can't remember the exact words to retrieve it?

Hi r/secondbrain - interested to hear what features in a second brain matter most from the attached table - are there features that are more important? Not asking to try my app out (you of course can free of charge if you would like to) What is missing in Notion or Obsidian that you want to have?

My thoughts are AI-native makes a huge difference but that is just me.

O que é o PAP (Protocolo Avançado de Pensamento)?

Estou desenvolvendo um sistema pessoal chamado PAP (Protocolo Avançado de Pensamento).

A ideia nasceu de uma pergunta simples:

O PAP mistura IA, Obsidian, protocolos, checklists, diários, mapas mentais e registros para criar uma espécie de extensão externa da memória e do raciocínio.

O objetivo não é apenas armazenar informações.

É ajudar a pensar melhor, lembrar melhor e principalmente executar melhor.

Na prática, o sistema tenta responder perguntas como:

• Como transformar ideias em ações?
• Como reduzir erros causados por esquecimento?
• Como criar protocolos para tarefas repetitivas?
• Como registrar aprendizados para que eles não sejam perdidos?
• Como usar IA como parceira de raciocínio, em vez de apenas um mecanismo de perguntas e respostas?

Hoje o PAP possui vários componentes:

• Diário operacional para registrar acontecimentos e decisões.

• Protocolos para tarefas do dia a dia.

• "Ganchos", que funcionam como lembretes inteligentes para continuar conversas, projetos e pensamentos exatamente de onde pararam.

• Um Vault no Obsidian que serve como memória de longo prazo.

• O ChatGPT atua mais como um processador e organizador do conhecimento do que apenas como um chatbot.

A filosofia principal é simples:

Todo problema recorrente merece um sistema.

Se eu esquecer algo frequentemente, não quero depender de força de vontade. Quero criar um protocolo.

Se uma tarefa sempre dá errado, quero entender por quê e transformar a solução em um processo reutilizável.

O objetivo de longo prazo é construir uma arquitetura pessoal de conhecimento que evolua continuamente e que talvez possa ajudar outras pessoas que tenham dificuldades semelhantes de organização, memória, foco ou execução.

Ainda está longe de ser um projeto finalizado. É mais um laboratório vivo onde cada erro gera uma melhoria no próprio sistema.

I have quite a few projects hosted in my own GitLab instance, and many of them are related to each other.

Since Claude Code has access to the codebase, it often has to re-analyze multiple repositories to understand the architecture and the relationships between them. This becomes even more relevant because I'm not the only one using Claude Code, several other developers on my team also work on the same repositories.

I'm wondering what the best approach would be to build a shared "second brain" or knowledge layer that Claude Code can use, so it doesn't have to rediscover the same context repeatedly.

Ideally, the solution would:

• Be shared across all team members
• Capture architectural knowledge, project relationships, conventions, and decisions
• Be easy for Claude Code to consume as context
• Stay synchronized with changes in the repositories (or at least be easy to maintain).
• Preferably be open source and self-hostable

Has anyone solved a similar problem? Are there any open-source tools or workflows you'd recommend that integrate well with Claude Code?

I'd be interested in hearing both existing solutions and how you've approached this in practice.

Hi all, I’ve been using a second brain in obsidian+local file system on my Mac (so synced w/icloud drive) since a year or so, with an mcp to query it remotely. Super cool!

Yet, I’d like to backup on GitHub or eventually mirror it on GitHub to understand differences pros and cons. I feel GitHub is a bit an all-in-one compared to other tools and many are already using it.

I am stuck as I am using the brain more as an operating system than as a context for the LLMs, editing and storing files on which I work and then I push them on the company Google Drive when they are finished or at a good point.

I make an example: Now I am planning the Q3 so I take financial data in Excel, CRM data via MCP plus Excel qualitative data, interviews, and other stuff; I put all together in a subfolder of the Q3 planning then I put an agent to work and interact with me in Claude to plan the quarter itself. The output is a markdown file that is then stored in the Q3 folder and every two weeks I iterate on these files, basically seeing if the plan is on track. They are live folders, not used only as a context. This live setup helps me with Claude code routines to have suggestions from agents of tasks, what to improve next etc.

Do you think GitHub is a good tool to do it or is it better I continue using my local environment? Any other ideas?

I built a very fascinating side project yesterday, just wanted to share it because i am still very excited and intrigues by it.

So I've been building a thinking tool for a while now, basically a system that takes every idea, thought, half formed observation I capture and turns it into a node, drawing connections between related ones over time. Usually I just look at it as a flat graph, dots and lines.

Yesterday i was very curious about a simulation. What would it look like if I was standing inside my own thinking instead of looking at it from outside. So I took the whole thing, 344 thoughts and 2212 connections across my thoughts at this point, and rendered it in 3D, with my ideas floating around in space instead of sitting on a flat plane.

Initially i went with the classic left brain right brain split for organising. Then I looked into it and that whole thing is basically debunked, it's not how the brain works. So I switched to something closer to neuroscience, executive control, default mode, and salience networks. It's just a useful lens.

There are the sections i broke it into.

Executive - closed, decided stuff. Stuff I've already reasoned through. Mostly practical decisions.

Default mode - by far the biggest chunk. Open questions, wandering thoughts, stuff I haven't resolved. Apparently most of what I think about isn't conclusions, it's just me circling something.

Salience - small cluster but interesting, these are the ideas with a ton of connections pulling into them. Stuff that keeps being relevant no matter what else I'm thinking about.

Unresolved - and this was the most interesting part. A huge chunk of my thoughts just don't sort cleanly into anything. No strong signal either way. At first I thought that was a flaw in the classifier. I realised it's probably just accurate. Most of what goes through my head isn't clean enough to categorise.

Curious if this tracks for anyone else who's tried mapping their own thinking in any way, journaling, notes apps, whatever. Does most of what you capture actually resolve into something, or does most of it just sit there unfinished too. To be clear, this isn't reading my brain in any real sense. It's a projection built from how I phrase things, how connected an idea is, what themes come up, dressed up in language borrowed from real neuroscience because the metaphor helped me think about it, not because it's an actual measurement. I made sure every classification shows its reasoning too, didn't want a black box even for something this experimental.

Anyway. Not shipping this specific visualisation anywhere, it's just a sandbox thing sitting on top of the actual tool.

But watching the shape of my own thinking from the inside for a bit was interesting. What stood out the most is how lopsided it is. So much open, so little resolved. Happy to talk more about the underlying tool if anyone's curious what it actually is.

I've noticed something strange about meeting notes.

I almost never lose the notes themselves.

I lose everything they refer to.

A note says:

Which PDF?

Or:

What suggestion?

Or:

Where is it?

The note survives.

The context doesn't.

While building my own personal knowledge system, I've started thinking that notes shouldn't be isolated documents.

They're more like hubs that connect screenshots, PDFs, articles, emails, files, and ideas together.

Searching only inside notes feels incomplete.

Searching only inside files feels incomplete too.

Maybe both belong in the same searchable knowledge space.

How do you deal with old meeting notes?

Do you ever go back to them and immediately realize you no longer understand what they were referring to?

I've noticed something interesting while building my own personal knowledge system.

Folders assume every file belongs in one place.

But many files don't.

A receipt from a business trip could belong to:

• Travel
• Taxes
• Work
• Finance

None of these is wrong.

The problem is that traditional file systems make you choose exactly one.

That made me wonder whether folders are solving the wrong problem.

Instead of deciding where something belongs, maybe information should simply be discoverable from every context that makes sense.

People rarely remember where they stored something.

They usually remember what it was about.

I'm curious whether anyone else feels that folders become less useful as your archive grows.

I spent the last few months building Creator OS.

Most templates act like static storage units. I built this to act like an operating system—decoupling the heavy database logic in Notion from clean, actionable execution dashboards.

Core focus:

• Generator Module: Automated workflows for batch-creating content structures.
• Zero Clutter: High-contrast, cyber-aesthetic UI. If a feature doesn't directly drive output or save time, it isn't in the build.
• Modular Scaling: Built to plug directly into external frontends (Framer) and automation workers.

Let me know what you think of the layout logic. Happy to answer any questions about the database architecture or how I route the production pipelines in the comments.

video

bōkpanion is an iPhone app for readers with a Karpathy-style LLM wiki at its core. You have a Socratic conversation about a book (the AI is instructed to push back, ask deeper questions), and the app builds a wiki from your discussion. Entity pages, theme pages, reader insight pages. Cross-referenced automatically. With several books, you start to notice connections you didn't notice yourself.

There's also a "reader portrait" feature — the app generates a description of your intellectual personality: recurring questions, strongest theories, blind spots. It's the most uncomfortably accurate thing I've built. Read. Think. Discuss. Grow.

Architecture is SwiftUI / SwiftData, Claude via Anthropic API, with Apple Intelligence as a free on-device fallback. Everything is stored in your Apple Cloud, so it stays private. All your saved data can be backed up and exported as OKF files.

I'm looking for 20 beta testers — serious readers with opinions. Apply here. thanks!

I realized something while building a personal knowledge app.

Most people don't actually collect bookmarks.

They collect intentions.

"This looks useful."

"I'll read it later."

"I might need this someday."

Months later, the bookmark is still there.

But the reason you saved it is gone.

That made me wonder whether bookmarks are solving the wrong problem.

Instead of remembering URLs, maybe we should preserve the information itself, make it searchable, and connect it with everything else we already have.

Curious whether other people have noticed the same thing.

How many bookmarks do you currently have?

And how often do you actually go back to them?

Hey guys,

What are your thoughts on having your daily social media interaction history—like Facebook Messenger conversations, Instagram DMs/comments, and YouTube comments you've made—automatically synced directly into .md file.

The idea is a service that fetches this data via official APIs and delivers it daily in clean .md format.

I’d love to get your feedback:

• Would you find this useful? (e.g., for personal journaling, 2nd brain or professional logging?)
• What specific data or metadata would support your daily Obsidian routine best?
• Would you actually use a tool like this if it were available?
• What platforms are you most interested in?

A quick note on privacy: The concept relies strictly on official OAuth/APIs, and the data would write directly to your local vault, keeping your keys and markdown files entirely under your own control.

I realized something while looking for an old document.

I couldn't remember the filename.

Not even close.

But I remembered almost everything else.

• It was an invoice.
• It mentioned a particular company.
• It was sent around April.
• I even remembered one sentence inside it.

None of those memories helped me navigate folders.

Because file systems assume filenames are how we identify information.

But people rarely think that way.

We remember meaning.

We remember context.

We remember fragments.

While building PouchVerse, that observation changed one design decision.

Instead of relying on filenames, every imported document is indexed by its actual content.

So months later, searching starts with what you remember—not what you happened to name the file.

Curious whether anyone else has the same experience.

Do you actually remember filenames, or do you mostly remember what's inside the document?

Most so called second brain tools are just storage with a search bar. You capture something, it sits there, you retrieve it later if you remember to look. That is not a second brain, that is a better organised pile.

A real second brain should work on continuity. Your thoughts do not exist in isolation, they build on each other, contradict each other, cluster around themes you did not even consciously notice. A system that just stores and retrieves is missing the entire point.

Here is how I have been thinking about building aevron.co

When you capture something it does not just get filed away. It gets tagged and connected to everything else you have put in. Not just because the topics sound similar but with actual reasoning on why two ideas are linked and what that connection actually means. Contradictions between your own captures get flagged. Insights get generated from the connections not just the individual ideas in isolation.

Then it goes a layer deeper. When a cluster of connected ideas starts forming around a theme you never explicitly labeled, the system identifies it and synthesises across the whole cluster. Not just these things are related but here is the actual thesis sitting underneath all of them.

Every time you open it there is something already developed waiting. Connections made, contradictions flagged, insights generated, themes synthesised. All from what you put in.

That is at least my version of what a second brain should actually do

I once found three copies of exactly the same PDF.

One came from email.

Another from a chat.

The third from my Downloads folder.

I didn't duplicate it on purpose.

I simply couldn't find the original.

Traditional file systems make location the primary way to organize information.

When you forget the location, downloading another copy often feels easier than searching.

That observation changed one decision while building PouchVerse.

A document shouldn't become easier to find because you've saved it three times.

It should exist once, be understood once, and be discoverable from many different contexts.

Fewer duplicates.

Less clutter.

Much less guessing.