Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

1 Neural Network + Obsidian + Karpathy’s 1-file method = the most unhinged second brain build of 2026. It remembers everything you’ve ever done, and it costs $0 on top of what you already pay. The base is Karpathy’s append and review: 1 giant note, new thoughts stack on... top, old ones sink, every few days you reread and pull the survivors back up. No folders, no tags, no plugins the rereading IS the system, because review is what turns storage into thinking. The flaw: past 10,000 lines, no human rereads anything. That’s where the neural network takes over. You keep the note in Obsidian 1 vault, everything dumps to the top: ideas, links, meeting fragments, half-thoughts. You never organize, you only dump. It all lives as plain markdown on your own disk, and that detail is the whole trick. Because now you point Claude Code at the vault folder, and it reads every line you’ve ever written. “What did I think about pricing in March.” “Find the 3 ideas I keep circling.” “What did I drop that deserves a second look.” It answers from YOUR notes, with quotes, in 15 seconds. Then once a week, 1 prompt closes the loop: read the last 7 days, surface the 5 entries worth pulling back up, flag anything that contradicts what I wrote a month ago. The model does the sinking and surfacing Karpathy did by hand, and the note stays alive instead of turning into a graveyard. Week 1 feels like nothing. Week 4 you hit the first “I already solved this in January.” Month 3 you consult your past self more than Google. Most second brains die in 11 days under 40 plugins and 200 folders. This one is 1 file and a loop, and it compounds because dumping takes 0 discipline. Notion stores what you thought. This thing argues back.show more

West Lord

15,096 subscribers

24,679 views • 1 month ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.

West Lord

593,249 views • 2 months ago

THIS IS WHAT YOUR SECOND BRAIN SHOULD LOOK LIKE most people dump notes into obsidian and call it a second brain it’s not a second brain it’s a second drawer karpathy just dropped the pattern that changes this and it’s called the llm wiki every time you add a source ai reads it, extracts key claims, updates every connected note and flags contradictions your obsidian stops being an archive and starts being alive save this and show it to someone still using notion as a second brain full breakdown in the article ↓

THIS IS WHAT YOUR SECOND BRAIN SHOULD LOOK LIKE most people dump notes into obsidian and call it a second brain it’s not a second brain it’s a second drawer karpathy just dropped the pattern that changes this and it’s called the llm wiki every time you add a source ai reads it, extracts key claims, updates every connected note and flags contradictions your obsidian stops being an archive and starts being alive save this and show it to someone still using notion as a second brain full breakdown in the article ↓

leopardracer

123,618 views • 2 months ago

this is more useful than my entire degree Elon Musk's rocket company signed a $60,000,000,000 deal for Cursor in June, and eight days ago the two of them put a worker on sale for $200 a month: it gets its own computer in the cloud, signs into your accounts, clicks through your real apps, and hands back finished work instead of a draft for you to paste i ran one against my receipts folder on sunday and got back 14 filed, 2 it held because they needed a card number, and a saved method i never wrote myself Grok Bot is the one you train by doing your own job in front of it, and the whole handover fits in four messages tonight: 1. write out one job you did today the way you would brief a new hire: what has to be finished, which sites and files to work from, what to hand back, and where it stops and asks you 2. let it run once on something safe to get wrong, then correct the result until it is worth your name 3. say "save what we just did as a skill", and add the one rule about what always needs your approval 4. say "run that skill every weekday at 8 and post the result here. if the source is missing, tell me instead of using yesterday's numbers" xAI wrote that order into its own manual: one real job, then the saved method, then the clock. a schedule sitting on top of a method nobody checked replaces two hours of your clicking with two hours of your mistake turns out you never get to pick the brain, and that is the part i would argue about: the manual says there is no model picker for members or admins, no plan to add one, and the bill follows whichever model answered bookmark this, then open the piece below: which jobs deserve a worker of their own, and which ones quietly burn the seat ↓

this is more useful than my entire degree Elon Musk's rocket company signed a $60,000,000,000 deal for Cursor in June, and eight days ago the two of them put a worker on sale for $200 a month: it gets its own computer in the cloud, signs into your accounts, clicks through your real apps, and hands back finished work instead of a draft for you to paste i ran one against my receipts folder on sunday and got back 14 filed, 2 it held because they needed a card number, and a saved method i never wrote myself Grok Bot is the one you train by doing your own job in front of it, and the whole handover fits in four messages tonight: 1. write out one job you did today the way you would brief a new hire: what has to be finished, which sites and files to work from, what to hand back, and where it stops and asks you 2. let it run once on something safe to get wrong, then correct the result until it is worth your name 3. say "save what we just did as a skill", and add the one rule about what always needs your approval 4. say "run that skill every weekday at 8 and post the result here. if the source is missing, tell me instead of using yesterday's numbers" xAI wrote that order into its own manual: one real job, then the saved method, then the clock. a schedule sitting on top of a method nobody checked replaces two hours of your clicking with two hours of your mistake turns out you never get to pick the brain, and that is the part i would argue about: the manual says there is no model picker for members or admins, no plan to add one, and the bill follows whichever model answered bookmark this, then open the piece below: which jobs deserve a worker of their own, and which ones quietly burn the seat ↓

Argona

21,946 views • 24 days ago

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE FABLE 5 + OBSIDIAN Andrej Karpathy (openai co-founder) shared an architecture that turns Claude into a persistent second brain instead of a basic chat window how it works: > you point Claude Code at an Obsidian vault folder > you drop articles, PDFs, or video transcripts into raw folders > Claude reads the files, updates topic summaries, and cross-references everything > the knowledge base compounds like interest instead of resetting on every new chat the setup is simple: > install and create a local vault directory > open the directory in Claude Code and paste Karpathy's wiki prompt: > > let the agent generate raw, wiki, and CLAUDE.md schema directories > drop any text file into raw and tell the model to ingest it > ask questions across the whole vault and query compiled summaries this eliminates rag database overhead and keeps your local vault organized how do you manage your local knowledge base?

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE FABLE 5 + OBSIDIAN Andrej Karpathy (openai co-founder) shared an architecture that turns Claude into a persistent second brain instead of a basic chat window how it works: > you point Claude Code at an Obsidian vault folder > you drop articles, PDFs, or video transcripts into raw folders > Claude reads the files, updates topic summaries, and cross-references everything > the knowledge base compounds like interest instead of resetting on every new chat the setup is simple: > install and create a local vault directory > open the directory in Claude Code and paste Karpathy's wiki prompt: > > let the agent generate raw, wiki, and CLAUDE.md schema directories > drop any text file into raw and tell the model to ingest it > ask questions across the whole vault and query compiled summaries this eliminates rag database overhead and keeps your local vault organized how do you manage your local knowledge base?

Mr. Buzzoni

89,170 views • 2 months ago

Obsidian became a neural network with 184,320 links and now runs as the most powerful second brain ever built for $0. 12,480 notes in 1 vault, 0 folders, 0 tabs, and he hasn't opened Notion in 7 months. Every night at 2 AM Claude Code walks the vault, reads all 12,480 notes, embeds them, and hunts for the pairs that should be linked but never were. Last night it found 61 and he accepted all 61. That's the move nobody makes by hand, because 12,480 notes means 77 million possible pairs, and a human links maybe 4 a day while the agent links 61 while he sleeps. Capture takes 2 seconds, a voice memo lands as a note in 1.4, a clip becomes a linked node on its own friction is what kills a second brain so he deleted the friction. Recall latency sits at 38 milliseconds, which means the graph answers before he finishes doubting himself. 36 clusters formed without him, decay score holds at 0.03, and 97% of everything he ever wrote is still reachable, while most people's notes rot past 90% in a year and turn into a graveyard with good search. Yesterday it surfaced 9 forgotten notes, one of them 412 days old, and that one became a product he shipped 48 hours later. Plain .md files on a laptop, no cloud, no subscription, no company that can delete his brain on a Tuesday. The graph doesn't store what he knows. It stores what he'd never have connected alone.

Obsidian became a neural network with 184,320 links and now runs as the most powerful second brain ever built for $0. 12,480 notes in 1 vault, 0 folders, 0 tabs, and he hasn't opened Notion in 7 months. Every night at 2 AM Claude Code walks the vault, reads all 12,480 notes, embeds them, and hunts for the pairs that should be linked but never were. Last night it found 61 and he accepted all 61. That's the move nobody makes by hand, because 12,480 notes means 77 million possible pairs, and a human links maybe 4 a day while the agent links 61 while he sleeps. Capture takes 2 seconds, a voice memo lands as a note in 1.4, a clip becomes a linked node on its own friction is what kills a second brain so he deleted the friction. Recall latency sits at 38 milliseconds, which means the graph answers before he finishes doubting himself. 36 clusters formed without him, decay score holds at 0.03, and 97% of everything he ever wrote is still reachable, while most people's notes rot past 90% in a year and turn into a graveyard with good search. Yesterday it surfaced 9 forgotten notes, one of them 412 days old, and that one became a product he shipped 48 hours later. Plain .md files on a laptop, no cloud, no subscription, no company that can delete his brain on a Tuesday. The graph doesn't store what he knows. It stores what he'd never have connected alone.

Spike 1%

11,546 views • 24 days ago

IMAGINE YOUR NOTES APP LOOKING LIKE MISSION CONTROL this is what a second brain becomes when you stop treating it like a folder and start treating it like a system it's called omega. every note is a star. every connection is a line. and it tracks stats most people have never seen on their own knowledge: maturity: 58%. velocity: +196%. active clusters. hotspots. top hubs. it's telling you which ideas are growing, which ones are going stale, and where your thinking is actually concentrated your regular notes app has none of this. you dump things in and hope you find them later this treats your knowledge like a living thing you can measure and grow here's the part that matters: when you can see your second brain, you actually use it the graph pulls you back. the growing clusters make you want to feed them. the stats make it a game you want to keep playing most people's notes are a graveyard nobody visits this is the version that's alive

IMAGINE YOUR NOTES APP LOOKING LIKE MISSION CONTROL this is what a second brain becomes when you stop treating it like a folder and start treating it like a system it's called omega. every note is a star. every connection is a line. and it tracks stats most people have never seen on their own knowledge: maturity: 58%. velocity: +196%. active clusters. hotspots. top hubs. it's telling you which ideas are growing, which ones are going stale, and where your thinking is actually concentrated your regular notes app has none of this. you dump things in and hope you find them later this treats your knowledge like a living thing you can measure and grow here's the part that matters: when you can see your second brain, you actually use it the graph pulls you back. the growing clusters make you want to feed them. the stats make it a game you want to keep playing most people's notes are a graveyard nobody visits this is the version that's alive

Orlixx

30,261 views • 25 days ago

save these two free services. they are what i built my Polymarket strategies on, the ones paying me around $10,000 a month. what it looks like day to day: you ask any question about the market in plain words, Claude Code digs through the data and comes back with numbers. you become a quant researcher. 1 - poly_data one command and every Polymarket trade sits on your own disk. who bought, when, at what price, what size, and who was standing on the other side of it. my first sync pulled 3.1 million markets. you can pull apart the edge of any trader on Polymarket you like. first sync runs a few hours, leave it overnight, after that updates land in seconds. 2 - pendulumflow archive this one holds the book itself: what orders were sitting there, at what prices, what size, second by second, on every single market. 288 billion events recorded, and 2.3 billion more coming in every day. i used to pay $200 a month for this kind of data. here you just open it and take it, nothing to sign up for. the front page has ready made questions you copy straight into Claude Code. the project runs on donations, storing and serving this much data costs real money every month. so if you start using it, send the guy something, he is carrying all of it alone. these two will give you what only a handful of people on this market have.

save these two free services. they are what i built my Polymarket strategies on, the ones paying me around $10,000 a month. what it looks like day to day: you ask any question about the market in plain words, Claude Code digs through the data and comes back with numbers. you become a quant researcher. 1 - poly_data one command and every Polymarket trade sits on your own disk. who bought, when, at what price, what size, and who was standing on the other side of it. my first sync pulled 3.1 million markets. you can pull apart the edge of any trader on Polymarket you like. first sync runs a few hours, leave it overnight, after that updates land in seconds. 2 - pendulumflow archive this one holds the book itself: what orders were sitting there, at what prices, what size, second by second, on every single market. 288 billion events recorded, and 2.3 billion more coming in every day. i used to pay $200 a month for this kind of data. here you just open it and take it, nothing to sign up for. the front page has ready made questions you copy straight into Claude Code. the project runs on donations, storing and serving this much data costs real money every month. so if you start using it, send the guy something, he is carrying all of it alone. these two will give you what only a handful of people on this market have.

may.crypto {🦅}

24,594 views • 4 days ago

This Chinese guy built a Second Brain in Obsidian and every morning gets 3 trading ideas that brought him $180,000 in 6 months. Inside he runs a pipeline of 6 workflows on N8N that automatically pulls every read article, listened podcast, and voice note into a shared Obsidian vault, and a neural network analyst every morning at 6:00 finds connections between the fresh and the old and puts the 3 strongest trading ideas for the day into the inbox. No analytics desk, no Bloomberg terminal, no Telegram chats with traders. Just a Mac Mini by the wall, an iPhone in the pocket, and 1 local Obsidian vault. And traditional quant funds keep entire teams of 8 people on salary for the same flow of insights, while his expenses are only subscriptions to Readwise, Whisper API, and N8N hosting. 6 pipelines process about 200 sources a day and close the monthly API bill at about $120. The Mac Mini itself stores the entire vault and keeps the neural network analyst running 24/7, and from the iPhone the owner drops any idea he hears on the go into a Telegram bot, and it lands in the vault inbox in just 30 seconds. The starting instruction that sits in the VAULT.md file at the root of his vault looks like this: "you are the AI analyst of a solo trader. you read his vault every morning at 6:00, find connections between fresh and old notes, and deliver 3 trading ideas he can verify in the hour before the market opens. pipelines: // Reader (pulls every article and highlight from Readwise, Twitter bookmarks, and Kindle into /notes) // Listener (transcribes podcasts through Airr and voice notes through Whisper, puts them in /notes) // Catcher (accepts any message from the Telegram bot and writes it to /inbox with a timestamp) // Connector (every night reads across the entire vault and updates the connection graph between 4,000 notes) // Briefer (at 6:00 AM writes a brief: 3 trading ideas for today plus the emerging thesis of the week, puts it in /inbox) // Mobile (lives in the iPhone, answers any question about the vault by voice, and confirms alerts while the owner is on the go). you wake the owner with a push notification only when a fresh note contradicts his active thesis or when 1 of the 3 morning ideas has a confidence score above 90%." This instruction immediately sets the role for the system and the limits of its autonomy. It knows it is supposed to connect new with old on its own. It knows it is supposed to prepare 3 trading ideas every morning on its own. It knows it connects the live trader only when a thesis is contradicted or an ultra-confident idea appears. → Reader pulls about 80 articles and highlights a day from Readwise, Twitter, and Kindle → Listener transcribes 4 to 6 podcasts a week through Airr and Whisper → Catcher intercepts all voice and text ideas through the Telegram bot, averaging 15 to 20 a day → Connector updates the connection graph between 4,000 notes every night, adding 25 to 30 new edges → Briefer puts a fresh brief with 3 trading ideas and the emerging thesis into the inbox at exactly 6:00 → Mobile answers any question about the vault by voice and confirms alerts right from the iPhone And only when a new note contradicts his active thesis or 1 of the ideas breaks 90% confidence does the orchestrator raise the owner with a push notification. And when the trader at that moment is driving to the gym or eating breakfast, the Mobile agent in his iPhone answers any quick question about the vault by voice: what he wrote about this ticker last week, which 3 sources support the idea of long NVDA, and what counter-thesis already sits in his notes. The trader makes the decision and sends the order before New York opens. The fresh brief from last Monday looks like this: "reader: 78 materials added over the weekend, 11 of them about semiconductors, 4 about energy, 3 about biotech. passing to connector." "connector: 27 new connections found between fresh materials and the vault, the strongest one is that the Goldman report from Wednesday matches the NVDA thesis you wrote 3 weeks ago." "briefer: 3 trading ideas for today: long NVDA (confidence 0.84), short Tesla at the close of the quarterly report (0.71), watch URI (0.62). emerging thesis of the week: the market is underpricing capex on data centers." "alert: your fresh note about long-term risk in semis contradicts the NVDA thesis. sending for review." In his work setup there is no cloud server, no team of analysts, and not even a Bloomberg subscription. At home sits a Mac Mini with a local Obsidian vault, on top run 6 N8N pipelines and a neural network analyst, and the same vault mirrors to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo trading setup on a second brain: $120 a month on the API, about $30,000 a month into the account, and between them 6 pipelines, 4,000 connected notes, and 1 iPhone in the pocket.

This Chinese guy built a Second Brain in Obsidian and every morning gets 3 trading ideas that brought him $180,000 in 6 months. Inside he runs a pipeline of 6 workflows on N8N that automatically pulls every read article, listened podcast, and voice note into a shared Obsidian vault, and a neural network analyst every morning at 6:00 finds connections between the fresh and the old and puts the 3 strongest trading ideas for the day into the inbox. No analytics desk, no Bloomberg terminal, no Telegram chats with traders. Just a Mac Mini by the wall, an iPhone in the pocket, and 1 local Obsidian vault. And traditional quant funds keep entire teams of 8 people on salary for the same flow of insights, while his expenses are only subscriptions to Readwise, Whisper API, and N8N hosting. 6 pipelines process about 200 sources a day and close the monthly API bill at about $120. The Mac Mini itself stores the entire vault and keeps the neural network analyst running 24/7, and from the iPhone the owner drops any idea he hears on the go into a Telegram bot, and it lands in the vault inbox in just 30 seconds. The starting instruction that sits in the VAULT.md file at the root of his vault looks like this: "you are the AI analyst of a solo trader. you read his vault every morning at 6:00, find connections between fresh and old notes, and deliver 3 trading ideas he can verify in the hour before the market opens. pipelines: // Reader (pulls every article and highlight from Readwise, Twitter bookmarks, and Kindle into /notes) // Listener (transcribes podcasts through Airr and voice notes through Whisper, puts them in /notes) // Catcher (accepts any message from the Telegram bot and writes it to /inbox with a timestamp) // Connector (every night reads across the entire vault and updates the connection graph between 4,000 notes) // Briefer (at 6:00 AM writes a brief: 3 trading ideas for today plus the emerging thesis of the week, puts it in /inbox) // Mobile (lives in the iPhone, answers any question about the vault by voice, and confirms alerts while the owner is on the go). you wake the owner with a push notification only when a fresh note contradicts his active thesis or when 1 of the 3 morning ideas has a confidence score above 90%." This instruction immediately sets the role for the system and the limits of its autonomy. It knows it is supposed to connect new with old on its own. It knows it is supposed to prepare 3 trading ideas every morning on its own. It knows it connects the live trader only when a thesis is contradicted or an ultra-confident idea appears. → Reader pulls about 80 articles and highlights a day from Readwise, Twitter, and Kindle → Listener transcribes 4 to 6 podcasts a week through Airr and Whisper → Catcher intercepts all voice and text ideas through the Telegram bot, averaging 15 to 20 a day → Connector updates the connection graph between 4,000 notes every night, adding 25 to 30 new edges → Briefer puts a fresh brief with 3 trading ideas and the emerging thesis into the inbox at exactly 6:00 → Mobile answers any question about the vault by voice and confirms alerts right from the iPhone And only when a new note contradicts his active thesis or 1 of the ideas breaks 90% confidence does the orchestrator raise the owner with a push notification. And when the trader at that moment is driving to the gym or eating breakfast, the Mobile agent in his iPhone answers any quick question about the vault by voice: what he wrote about this ticker last week, which 3 sources support the idea of long NVDA, and what counter-thesis already sits in his notes. The trader makes the decision and sends the order before New York opens. The fresh brief from last Monday looks like this: "reader: 78 materials added over the weekend, 11 of them about semiconductors, 4 about energy, 3 about biotech. passing to connector." "connector: 27 new connections found between fresh materials and the vault, the strongest one is that the Goldman report from Wednesday matches the NVDA thesis you wrote 3 weeks ago." "briefer: 3 trading ideas for today: long NVDA (confidence 0.84), short Tesla at the close of the quarterly report (0.71), watch URI (0.62). emerging thesis of the week: the market is underpricing capex on data centers." "alert: your fresh note about long-term risk in semis contradicts the NVDA thesis. sending for review." In his work setup there is no cloud server, no team of analysts, and not even a Bloomberg subscription. At home sits a Mac Mini with a local Obsidian vault, on top run 6 N8N pipelines and a neural network analyst, and the same vault mirrors to a secure terminal on the iPhone. Out of everything I have seen this year, this is the cleanest solo trading setup on a second brain: $120 a month on the API, about $30,000 a month into the account, and between them 6 pipelines, 4,000 connected notes, and 1 iPhone in the pocket.

Blaze

929,858 views • 4 months ago

this is f**king dangerous Most people treat Claude like a search bar. The ones with a second brain treat it as an intelligence layer on everything they know. Here's the 15-minute setup: → Install Claude Code → Install Obsidian, create a vault → Open it in Claude Code, drop in the CLAUDE.md schema — that one file is the engine → Throw any source in, say "ingest this" Done. From then on, everything you know is queryable by the most capable AI on earth. Claude wires each source against your whole vault and surfaces connections you forgot you had. Build it tonight. full A–Z guide below.

this is f**king dangerous Most people treat Claude like a search bar. The ones with a second brain treat it as an intelligence layer on everything they know. Here's the 15-minute setup: → Install Claude Code → Install Obsidian, create a vault → Open it in Claude Code, drop in the CLAUDE.md schema — that one file is the engine → Throw any source in, say "ingest this" Done. From then on, everything you know is queryable by the most capable AI on earth. Claude wires each source against your whole vault and surfaces connections you forgot you had. Build it tonight. full A–Z guide below.

Kirill

19,358 views • 1 month ago

Claude, Obsidian and n8n form a second brain that clears $5,200 months from brand UGC deals. Most creators still open a blank CapCut file and hope the brand brief sticks. That loop dies at $1,800. The stack replaces hope with a closed system. Obsidian holds every brand voice, every past script that hit 400k views, every rejection note. Claude reads the vault through a local project and rewrites the next five UGC packages in 3 minutes. n8n watches the inbox, creates the note, triggers Claude, formats the brief, and drops the finished package into the brand portal while the creator sleeps. No more research tabs. No more “what angle worked last time.” Month 1: build the vault and wire the three tools. Month 2: first automated batch ships. Two brands pay $1,100 total. Month 3: the same loop runs on four brands. Average deal $480. Twelve packages leave. Bank shows $5,200. The second brain does not store notes. It compounds every win into the next model. Script that scored 18% engagement gets tagged. Claude pulls only those tags next run. The model improves without extra prompt engineering. UGC brands pay for consistency, not inspiration. This system delivers the same quality every week at the same speed. Set the vault once. Let the three tools run the rest. If this was useful - follow.

Rugikk

10,318 views • 1 month ago

✨ [ This week on ] is finally live because Piotrek Bodera asked me to finish it and then I in turn asked Claude Code to finish it 😝 It goes into members chat and summarizes what happened in the top channels this week It also checks your current location (for me Brazil) and puts that channel on top of the email, because that's most relevant for you If you click the channel it deep links you into that country's channel in Telegram, and if you click a user it goes to their web profile It's a fun way to stay up to date and also keep people involved in the chat (the core of the community) 😊👌 ✅ Another todo wiped off my list!

@levelsio

16,469 views • 6 months ago

I don't care about what you want. I care about what you repeat. Because your brain does not run on intention. It runs on repetition. Every thought you keep returning to, your brain treats as a signal. And the more you send that signal, the stronger and faster that neural pathway becomes. Here is the science behind it. When you repeatedly activate a neural pathway, your brain wraps a fatty substance called myelin around it. Think of it like insulation around an electrical wire. The more myelin, the faster the signal travels. The faster the signal travels, the more automatic that thought or behavior becomes. This is Hebb's Law. Neurons that fire together, wire together. And here is the part most people miss. Your brain does not care what you are reinforcing. It does not filter for good or bad. It just responds to what you keep repeating. Repeat confidence. Your brain builds it. Repeat self-doubt. Your brain builds that too. The same biological process that wires in focus, discipline, and certainty is the exact same one wiring in anxiety, fear, and limitation. You are not wired a certain way forever. You are wired for whatever you keep practicing. So stop asking what you want to change. Start asking what you are willing to repeat. ✨🙌🏾💫

I don't care about what you want. I care about what you repeat. Because your brain does not run on intention. It runs on repetition. Every thought you keep returning to, your brain treats as a signal. And the more you send that signal, the stronger and faster that neural pathway becomes. Here is the science behind it. When you repeatedly activate a neural pathway, your brain wraps a fatty substance called myelin around it. Think of it like insulation around an electrical wire. The more myelin, the faster the signal travels. The faster the signal travels, the more automatic that thought or behavior becomes. This is Hebb's Law. Neurons that fire together, wire together. And here is the part most people miss. Your brain does not care what you are reinforcing. It does not filter for good or bad. It just responds to what you keep repeating. Repeat confidence. Your brain builds it. Repeat self-doubt. Your brain builds that too. The same biological process that wires in focus, discipline, and certainty is the exact same one wiring in anxiety, fear, and limitation. You are not wired a certain way forever. You are wired for whatever you keep practicing. So stop asking what you want to change. Start asking what you are willing to repeat. ✨🙌🏾💫

🧬Maxpein🧬

54,705 views • 1 month ago

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?

Mr. Buzzoni

15,682 views • 25 days ago

Every thought you repeat is training your brain. Including the ones destroying you. Every repeated thought is a tiny vote for what your brain should make easier next time. That’s the strange thing about your brain. It doesn’t only learn the things you sit down and decide to learn. It learns what you rehearse. The worry you revisit. The story you keep telling yourself. The reaction you repeat. But also the skill you practice, the courage you keep choosing, and the new response that feels awkward at first. None of those repetitions feels life-changing in the moment. But your brain is paying attention. (This is What Happens in Your Brain When You Learn Something New)

Every thought you repeat is training your brain. Including the ones destroying you. Every repeated thought is a tiny vote for what your brain should make easier next time. That’s the strange thing about your brain. It doesn’t only learn the things you sit down and decide to learn. It learns what you rehearse. The worry you revisit. The story you keep telling yourself. The reaction you repeat. But also the skill you practice, the courage you keep choosing, and the new response that feels awkward at first. None of those repetitions feels life-changing in the moment. But your brain is paying attention. (This is What Happens in Your Brain When You Learn Something New)

Mind Essentials

49,904 views • 2 days ago

sorry, they just did WHAT someone gave a machine one disease name, the leading cause of blindness in the developed world with 1.5 million americans already in its path, and it came back pointing at a drug that has sat in pharmacies for years under a different label: 551 papers read in 30 minutes against the 294 hours a human would have needed, and the loop that did it is public on GitHub most agent setups answer one question at a time, so the ceiling on the work is the quality of the question you happened to think of this one was handed a single question and wrote the second one itself. turns out that follow-up is where the real find was: a target called ABCA1, upregulated threefold, in an experiment no human ordered i read the whole paper looking for the trick, and the trick is structural. that is the second question, and it is the gap between an assistant and a factory: - hand the loop a field rather than a task: it was given a disease, and choosing the mechanism was part of its job - make it rank before it spends: 151 papers in, ten candidate mechanisms out, scored against each other before anything touched a bench - split reading from judging, so the agent that forms the theory is a different agent from the one grading it - close every cycle on physical reality: the verdict was an experiment, and another model's opinion was never allowed to stand in for one - feed each result back as the next question rather than a log line, which is the step almost nobody builds - search what already passed inspection first: the winner was an approved compound with a safety file already on record - write down what the round learned before opening the next one, so round two starts where round one stopped my read, and i think it is the uncomfortable one: reading was the entire bottleneck in that field, and everybody spent the decade optimising the writing. people ran every physical experiment here, the analysis agent needs a domain expert writing its prompts, and the authors decline to call this the leap it resembles. the thinking got replaced, and the hands did not so the question i cannot answer for my own setup: which step of your loop still stops dead until you sit down and type something bookmark this one. the four parts that turn one model into a line that runs like this, the queue, the rooms, the write permissions and the gate, are built file by file in the piece below ↓

sorry, they just did WHAT someone gave a machine one disease name, the leading cause of blindness in the developed world with 1.5 million americans already in its path, and it came back pointing at a drug that has sat in pharmacies for years under a different label: 551 papers read in 30 minutes against the 294 hours a human would have needed, and the loop that did it is public on GitHub most agent setups answer one question at a time, so the ceiling on the work is the quality of the question you happened to think of this one was handed a single question and wrote the second one itself. turns out that follow-up is where the real find was: a target called ABCA1, upregulated threefold, in an experiment no human ordered i read the whole paper looking for the trick, and the trick is structural. that is the second question, and it is the gap between an assistant and a factory: - hand the loop a field rather than a task: it was given a disease, and choosing the mechanism was part of its job - make it rank before it spends: 151 papers in, ten candidate mechanisms out, scored against each other before anything touched a bench - split reading from judging, so the agent that forms the theory is a different agent from the one grading it - close every cycle on physical reality: the verdict was an experiment, and another model's opinion was never allowed to stand in for one - feed each result back as the next question rather than a log line, which is the step almost nobody builds - search what already passed inspection first: the winner was an approved compound with a safety file already on record - write down what the round learned before opening the next one, so round two starts where round one stopped my read, and i think it is the uncomfortable one: reading was the entire bottleneck in that field, and everybody spent the decade optimising the writing. people ran every physical experiment here, the analysis agent needs a domain expert writing its prompts, and the authors decline to call this the leap it resembles. the thinking got replaced, and the hands did not so the question i cannot answer for my own setup: which step of your loop still stops dead until you sit down and type something bookmark this one. the four parts that turn one model into a line that runs like this, the queue, the rooms, the write permissions and the gate, are built file by file in the piece below ↓

Argona

32,475 views • 1 month ago

you've read 200 articles this year. you remember maybe 5. the other 195 didn't vanish because you're forgetful — they vanished because they had nowhere to live. no system caught them, so they slipped straight through. here's the fix — Karpathy's second-brain method: > drop anything into one folder: an article, a PDF, a transcript > Claude breaks it into atomic notes and links each one to what's already there > nothing sits alone — every new source makes the whole vault sharper > then you stop searching and just ask, pulling from all of it at once three folders. one config file. set up before your coffee's done. no more cold starts — every session builds on everything you know. full A–Z guide below.

you've read 200 articles this year. you remember maybe 5. the other 195 didn't vanish because you're forgetful — they vanished because they had nowhere to live. no system caught them, so they slipped straight through. here's the fix — Karpathy's second-brain method: > drop anything into one folder: an article, a PDF, a transcript > Claude breaks it into atomic notes and links each one to what's already there > nothing sits alone — every new source makes the whole vault sharper > then you stop searching and just ask, pulling from all of it at once three folders. one config file. set up before your coffee's done. no more cold starts — every session builds on everything you know. full A–Z guide below.

Kirill

32,930 views • 1 month ago

I still don't understand why everyone is not using this yet. Thanks to it, a year ago I increased my income to 17,000 dollars a month Andrey Karpathy, co-founder of OpenAI, published a simple idea that got 16 million views: stop using AI to write code, use it to build a second brain You point Claude Code to a folder, drop any source in there (an article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. It compounds like interest: the more you feed it, the smarter it gets Here is the gist: Install Obsidian, create a vault, open it in Claude Code Paste the file with Karpathy's wiki idea and tell Claude to build it Claude creates three folders: raw for sources, wiki for its pages, CLAUDE which runs everything Drop any source into raw and say "ingest this" Ask questions across everything, forever Five minutes to set up, and you never start with an empty chat again The full step-by-step guide is in the article. Save to bookmarks

I still don't understand why everyone is not using this yet. Thanks to it, a year ago I increased my income to 17,000 dollars a month Andrey Karpathy, co-founder of OpenAI, published a simple idea that got 16 million views: stop using AI to write code, use it to build a second brain You point Claude Code to a folder, drop any source in there (an article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. It compounds like interest: the more you feed it, the smarter it gets Here is the gist: Install Obsidian, create a vault, open it in Claude Code Paste the file with Karpathy's wiki idea and tell Claude to build it Claude creates three folders: raw for sources, wiki for its pages, CLAUDE which runs everything Drop any source into raw and say "ingest this" Ask questions across everything, forever Five minutes to set up, and you never start with an empty chat again The full step-by-step guide is in the article. Save to bookmarks

Bober_smart

2,822,919 views • 22 days ago

A STANFORD GUY POINTED CLAUDE CODE AT 11,400 OBSIDIAN NOTES AND FOUND 214 ARGUMENTS HE'D HAD WITH HIMSELF 7 years of notes, 340MB of markdown, and a graph view that looked like a brain but never once thought. Every Sunday he opened the vault and every Sunday he closed it again. The second brain was a landfill with good lighting. So he stopped reading it and let something else read it instead. 47 lines of config, one instruction: find every pair of notes written 2+ years apart that contradict each other. 19 minutes on a 2021 MacBook Air, then 214 pairs. He had changed his mind 214 times in 7 years and caught himself doing it zero times. Then came the one that stopped him a note from March 2019, 62 words, sitting in a folder called "misc," describing the exact product he'd spent the last 5 months and $18,000 building a research doc around. He solved it in 2019, filed it, and forgot it existed. The vault never failed him, it stored all of it perfectly, it just had no way to speak. Now a cron job wakes at 6 AM, reads 40 notes, and writes 1 paragraph: here's what you believed then, here's what you believe now, here's the gap. He hasn't opened the graph view since. He didn't need a second brain, he needed the first one to answer back.

A STANFORD GUY POINTED CLAUDE CODE AT 11,400 OBSIDIAN NOTES AND FOUND 214 ARGUMENTS HE'D HAD WITH HIMSELF 7 years of notes, 340MB of markdown, and a graph view that looked like a brain but never once thought. Every Sunday he opened the vault and every Sunday he closed it again. The second brain was a landfill with good lighting. So he stopped reading it and let something else read it instead. 47 lines of config, one instruction: find every pair of notes written 2+ years apart that contradict each other. 19 minutes on a 2021 MacBook Air, then 214 pairs. He had changed his mind 214 times in 7 years and caught himself doing it zero times. Then came the one that stopped him a note from March 2019, 62 words, sitting in a folder called "misc," describing the exact product he'd spent the last 5 months and $18,000 building a research doc around. He solved it in 2019, filed it, and forgot it existed. The vault never failed him, it stored all of it perfectly, it just had no way to speak. Now a cron job wakes at 6 AM, reads 40 notes, and writes 1 paragraph: here's what you believed then, here's what you believe now, here's the gap. He hasn't opened the graph view since. He didn't need a second brain, he needed the first one to answer back.

Spike 1%

18,386 views • 25 days ago

A CHINESE TRADER BUILT A SECOND BRAIN IN OBSIDIAN THAT GENERATES 3 TRADING IDEAS EVERY MORNING AT 6AM AND MADE $180,000 IN 6 MONTHS. No Bloomberg terminal. No analytics desk. No team of analysts. A Mac Mini by the wall. An iPhone in his pocket. One local Obsidian vault. Six N8N pipelines running 24/7, pulling every article he reads, every podcast he listens to, and every voice note he drops into a Telegram bot—directly into the vault. Every night, a neural network reads across 4,000 connected notes and finds the strongest connections between fresh information and old theses. Every morning at 6AM, a brief lands in his inbox: - 3 trading ideas with confidence scores - The emerging thesis of the week - Any note that contradicts an active position The system only wakes him up when a fresh note contradicts his thesis, or when an idea breaks 90% confidence. Everything else runs without him. The monthly bill: $120 in API costs. The monthly return: approximately $30,000 into the account. Traditional quant funds pay teams of 8 people to produce the same flow of insights. He pays $120 and a Mac Mini. The full system breakdown is in the article below. Bookmark this before you pay for a Bloomberg subscription.

A CHINESE TRADER BUILT A SECOND BRAIN IN OBSIDIAN THAT GENERATES 3 TRADING IDEAS EVERY MORNING AT 6AM AND MADE $180,000 IN 6 MONTHS. No Bloomberg terminal. No analytics desk. No team of analysts. A Mac Mini by the wall. An iPhone in his pocket. One local Obsidian vault. Six N8N pipelines running 24/7, pulling every article he reads, every podcast he listens to, and every voice note he drops into a Telegram bot—directly into the vault. Every night, a neural network reads across 4,000 connected notes and finds the strongest connections between fresh information and old theses. Every morning at 6AM, a brief lands in his inbox: - 3 trading ideas with confidence scores - The emerging thesis of the week - Any note that contradicts an active position The system only wakes him up when a fresh note contradicts his thesis, or when an idea breaks 90% confidence. Everything else runs without him. The monthly bill: $120 in API costs. The monthly return: approximately $30,000 into the account. Traditional quant funds pay teams of 8 people to produce the same flow of insights. He pays $120 and a Mac Mini. The full system breakdown is in the article below. Bookmark this before you pay for a Bloomberg subscription.

CyrilXBT

46,087 views • 2 months ago

an agent is four parts in a loop. you own one. the other three break it. that's why the demo works and prod doesn't. you can't debug what you can't see. 1) the prompt → what you tell the model each turn. you own this one. good. 2) the context window → what it sees right now. the framework fills it with junk, and you never notice until it rots. 3) the tools → what it can do. you own the list, not when or why it fires them. 4) the control flow → what happens next, when to stop. the framework owns this. it's what breaks at 80%. own all four and your agent stops being a magic trick that works on stage and dies on call. this isn't my idea. it's the 12-factor agents guide (24k stars) github: the whole thing every serious builder ends up rewriting their stack around. full breakdown in the article below.

an agent is four parts in a loop. you own one. the other three break it. that's why the demo works and prod doesn't. you can't debug what you can't see. 1) the prompt → what you tell the model each turn. you own this one. good. 2) the context window → what it sees right now. the framework fills it with junk, and you never notice until it rots. 3) the tools → what it can do. you own the list, not when or why it fires them. 4) the control flow → what happens next, when to stop. the framework owns this. it's what breaks at 80%. own all four and your agent stops being a magic trick that works on stage and dies on call. this isn't my idea. it's the 12-factor agents guide (24k stars) github: the whole thing every serious builder ends up rewriting their stack around. full breakdown in the article below.

Hanako

38,184 views • 1 month ago