Second Brain Now Answers Questions About Itself
Months of telling people to put their important information somewhere AI can query it, and we had never done it for our own product.
A user asked Claude how tagging works when importing data into Second Brain.
Claude answered. The answer sounded perfectly reasonable. It was also wrong.
Claude did not have the information, so it did what AI does in that situation. It filled in the blanks.
Which is the exact problem we built Second Brain to solve.
Months of telling people to put their important information somewhere AI can query it, and we had never done it for our own product.
That is fixed now. The documentation lives inside the Second Brain knowledge base. It installs with the app and stays updated with it.
Connect Claude to Hexact (Second Brain) desktop app and you can ask:
What file formats can I import?
How many files can I import at once?
What happens if a file is unsupported?
How does OCR work?
Where is my database stored?
How do Stripe subscriptions connect to contacts?
What does Database Cleanup actually do?
Claude does not guess and does not search the web. It reads the documentation for the version of Second Brain you are actually running.
The better questions are not documentation questions.
Say you have four years of contracts, a Stripe export, a Gmail archive, and several folders of project files waiting to go in. Instead of working out the order yourself, ask:
“What should I import first, and is there anything I should organize before I start?”
Claude answers from how the app actually behaves, including the limits you are about to hit.
The same gap shows up in your business
Say you have three Claude chats open. One on pricing. One drafting an email campaign. One going through customer data.
In the pricing chat, you decide to move a promotion to September.
An hour later, the email chat needs the promotion dates. Does it know what you decided?
No.
So you tell it again, or paste from the other chat, or keep a document updated and remember to attach it every time.
That is the same failure as Claude guessing about tagging. The information exists. There is nowhere for Claude to look it up.
A database is somewhere to look.
Tell the pricing chat to write the decision to Second Brain, and the email chat can query it an hour later. Claude gets three tools through MCP: read the schema, run a query, write rows back. The third one is what makes the first two worth anything across sessions.
Need one customer’s history? It queries that customer’s records. Need a clause out of a 200-page contract? It pulls the sections that mention it instead of loading the file. Need to know how OCR works? Now it queries that too.
Claude does not need to know everything. It needs one place to look.
This gets harder the more data you have
Files in a Claude Project work fine, until there are enough of them that you start deciding what deserves to be in there. At that point you are curating context instead of working.
Second Brain holds years of information and Claude takes only what the current question needs.
No reloading the same files. No paying tokens to reread them. No carrying decisions between conversations by hand.
One database, any number of sessions, the same source of truth for all of them.
Try it
Update or download Second Brain at brain.hexact.io. There is a 7-day trial and no credit card required.
Connect Claude and ask:
“What can I import into Second Brain, and what are the import limits?”
The answer now comes from Second Brain itself.
Then ask it the question you actually care about. The one about your imports, your data, your setup.
If the answer does not cover it, book a video call and ask me instead. You get a real answer, and I find out what is missing from the documentation and add it.
We spent months telling people to put their knowledge into Second Brain. Eventually, we remembered to put ours there too.
