Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

holy sh*t. Karpathy's second brain pattern runs on Grok Bot now: stop explaining your life to AI from zero every chat, keep a wiki that writes itself three bots in one group chat, each with its own memory: the reader takes every link, PDF and voice note you drop... and never edits it the librarian rewrites every wiki page that source touches, usually 10 to 15 of them the checker wakes up on a nightly routine and hunts contradictions, stale claims and pages nothing links to → you ask a question: the answer gets filed back as a page, so the brain grows from use, not only from reading → a new source contradicts an old page: the checker tags you instead of quietly overwriting it → a page goes 30 days without a fresh source: it gets marked unconfirmed a second brain can sound sure while remembering the wrong thing Reader collects. Librarian writes. Checker doubts. every page has to show: > the claim > the source it came from > the date it was last confirmed paste this into Grok Bot: "Build me a second brain with three bots in one group chat. Keep my sources untouched in raw/, maintain wiki/ yourself, file good answers back as pages and run a nightly check for contradictions. Show me the structure first. Do not create anything until I confirm" start with one topic you actually work on, not your whole life full setup belowshow more

Argona

37,492 subscribers

505,244 Aufrufe • vor 8 Tagen •via X (Twitter)

Comedy Bildung Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

27 Kommentare

Profilbild von Avid

Avidvor 8 Tagen

This is crazy

Profilbild von Argona

Argonavor 8 Tagen

honestly crazy is the right word for this one

Profilbild von Michael Ten 🌨🎶🫐🍀

Michael Ten 🌨🎶🫐🍀vor 8 Tagen

What is this GUI? @grok

Profilbild von Roxx

Roxxvor 8 Tagen

how does the checker find contradictions, embedding distance or claim level diff?

Profilbild von Argona

Argonavor 8 Tagen

not sure, but pages keep claim and source, so claim-level fits

Profilbild von twinedon

twinedonvor 8 Tagen

reader collects, librarian writes, checker doubts, so clean

Profilbild von Frank Parro

Frank Parrovor 8 Tagen

@bot check out this for us

Profilbild von SOFIA

SOFIAvor 8 Tagen

Wow dudeee this is next lvl dev stuff

Profilbild von Aleiah

Aleiahvor 8 Tagen

This looks awsome have you built it or tried it at least ?

Profilbild von Argona

Argonavor 8 Tagen

didn't build it, it's karpathy's pattern, i just found and shared it

Profilbild von Necro

Necrovor 8 Tagen

@bot check this out for me

Profilbild von Larry

Larryvor 8 Tagen

@bot

Profilbild von Ben

Benvor 8 Tagen

Is this bullshit? Is this really karpathys design? Or adapted from something else.

Profilbild von Tony Z

Tony Zvor 8 Tagen

@bot 怎么指定某个 bot 来分析下内容

Profilbild von Security Unfiltered Podcast

Security Unfiltered Podcastvor 8 Tagen

This is really cool but how much of my usage will this use everyday?

Profilbild von Alessandro Moretti

Alessandro Morettivor 8 Tagen

The checker that doubts everything is the only bot I'd pay for.

Profilbild von Argona

Argonavor 8 Tagen

same, that one's worth paying for

Profilbild von Rigo

Rigovor 8 Tagen

Same pattern works way beyond notes. I run 10+ bots, each with one job and its own memory, and nothing leaves without my approval. Who decides what goes into the wiki in your setup, the reader bot or you?

Profilbild von Argona

Argonavor 8 Tagen

librarian writes it, reader never touches it, conflicts come to you

Profilbild von Fokki

Fokkivor 8 Tagen

Karpathy's is cooking again

Profilbild von Argona

Argonavor 8 Tagen

man keeps dropping patterns everyone ends up using

Profilbild von ZyMoProfit

ZyMoProfitvor 8 Tagen

How did you make this visual?

Profilbild von Argona

Argonavor 8 Tagen

it's a simulated clip, no robots were stressed making it

Profilbild von Gipp 🦅

Gipp 🦅vor 8 Tagen

grok bot, nightly checks keep the brain real

Profilbild von Argona

Argonavor 8 Tagen

gip doing nightly qa on a robot brain

Profilbild von Spikez 99.9%

Spikez 99.9%vor 8 Tagen

saved

Profilbild von Quentin Prévot

Quentin Prévotvor 8 Tagen

@bot ça peut tourner sur mon RAG avec des .md ?

Ähnliche Videos

🚨this broke my brain. i just watched a 20-something close his laptop, walk home and run his whole second brain from his phone (CEOs pay a chief of staff $135,000+ a year for the same job), while 99% of people still try to keep it all in their own head a second brain is one folder that knows everything you know, plus an AI that reads it before every task. Karpathy's post about it hit 22 million views you can build yours with Grok Bot tonight: - keep it in files, not chat memory. memory keeps summaries, a file stays exactly as you wrote it - never edit the originals. every note links back to the email or link it came from - slow facts like people and how you work live in files, fast facts like dates and amounts get rechecked at the source - one index file it reads first, then only the files that index points to - every correction becomes one line in a rules file it rereads before every task - skip the setup. grab the one-paste prompt from the article below and Grok Bot builds the whole brain for you it all runs on its own computer in the cloud, laptop shut at 7:30 every weekday one page is waiting with what came in, what it drafted and what waits for your yes zero re-explaining zero lost ideas zero blank chats it gets sharper every week you feed it you're done being your own memory you're running a second brain for $20 a month bookmark this. all 7 steps are in the article below

🚨this broke my brain. i just watched a 20-something close his laptop, walk home and run his whole second brain from his phone (CEOs pay a chief of staff $135,000+ a year for the same job), while 99% of people still try to keep it all in their own head a second brain is one folder that knows everything you know, plus an AI that reads it before every task. Karpathy's post about it hit 22 million views you can build yours with Grok Bot tonight: - keep it in files, not chat memory. memory keeps summaries, a file stays exactly as you wrote it - never edit the originals. every note links back to the email or link it came from - slow facts like people and how you work live in files, fast facts like dates and amounts get rechecked at the source - one index file it reads first, then only the files that index points to - every correction becomes one line in a rules file it rereads before every task - skip the setup. grab the one-paste prompt from the article below and Grok Bot builds the whole brain for you it all runs on its own computer in the cloud, laptop shut at 7:30 every weekday one page is waiting with what came in, what it drafted and what waits for your yes zero re-explaining zero lost ideas zero blank chats it gets sharper every week you feed it you're done being your own memory you're running a second brain for $20 a month bookmark this. all 7 steps are in the article below

Argona

28,538 Aufrufe • vor 11 Tagen

CLAUDE + OBSIDIAN + KARPATHY'S LLM WIKI = A WIKI THAT MAINTAINS ITSELF run this once and your research compounds instead of evaporating sources go in, a wiki comes out, and a loop keeps it honest • three layers, one owner each > the schema - CLAUDE.md, you and the agent co-evolve it > the wiki - markdown the agent owns. it writes, you read > raw sources - immutable, read only, never edited • three operations on repeat > ingest - read the source, write the summary, log one line > query - answer with citations, file it back as a new page > lint - contradictions, orphans and dead links caught early RAG re-derives the same answer from raw chunks on every query. you pay for that thinking again, every time you ask this wiki gets written once and stays current. 10-15 pages per source, nearly 100 sources on the index alone month one it saves you an hour a day. month six it knows your field better than the person you're up against for the senior seat "Obsidian is the IDE, the LLM is the programmer, the wiki is the codebase" - Andrej Karpathy the stack: 📁 Obsidian ↳ 📁 Claude ↳ 📁 Karpathy LLM-Wiki ↳

CLAUDE + OBSIDIAN + KARPATHY'S LLM WIKI = A WIKI THAT MAINTAINS ITSELF run this once and your research compounds instead of evaporating sources go in, a wiki comes out, and a loop keeps it honest • three layers, one owner each > the schema - CLAUDE.md, you and the agent co-evolve it > the wiki - markdown the agent owns. it writes, you read > raw sources - immutable, read only, never edited • three operations on repeat > ingest - read the source, write the summary, log one line > query - answer with citations, file it back as a new page > lint - contradictions, orphans and dead links caught early RAG re-derives the same answer from raw chunks on every query. you pay for that thinking again, every time you ask this wiki gets written once and stays current. 10-15 pages per source, nearly 100 sources on the index alone month one it saves you an hour a day. month six it knows your field better than the person you're up against for the senior seat "Obsidian is the IDE, the LLM is the programmer, the wiki is the codebase" - Andrej Karpathy the stack: 📁 Obsidian ↳ 📁 Claude ↳ 📁 Karpathy LLM-Wiki ↳

Annatar.md

16,939 Aufrufe • vor 1 Monat

someone on the Grok Bot team leaked this f*cking prompt online. paste this into Grok Bot. this one prompt builds a second brain that runs your life: -track what you're actually focused on every hour -write one page per person, project and decision -hunt its own contradictions every night -reject its own memory if it can't show the source Bookmark it right now.

someone on the Grok Bot team leaked this f*cking prompt online. paste this into Grok Bot. this one prompt builds a second brain that runs your life: -track what you're actually focused on every hour -write one page per person, project and decision -hunt its own contradictions every night -reject its own memory if it can't show the source Bookmark it right now.

Argona

60,694 Aufrufe • vor 8 Tagen

this in the wrong hands. jesus. Grok Bot turned a Gmail label into a second brain that's faster and better than any human Jason Freedman (YC alum and investor) gave Grok Bot four years of tax returns, 266 unlabeled files and one assignment: "please double check my CPA's work" label an email Brain and watch it land in the right folder with a summary, the date and a link to the raw source add a second bot while keeping the same folder. Lingxi Li at SpaceXAI could manage 15 cloud agents by hand, and with Grok Bot the fleet now manages more than 200 at once each routine gets one job and runs on its own clock: → 11 PM filing copies Brain-labelled mail into raw/ and sorts it into people/ or projects/ → 5 PM attention rewrites attention.md from what you actually touched → 7:30 AM page hands you facts, guesses and the drafts waiting for your yes → Sunday 6 PM review finds what you decided and forgot a great CPA with no AI tools missed HSA contributions counted twice, four years in a row, and mortgage interest left off the 2022 return entirely Brain reopens every number at the source, never from memory, and nothing is sent, bought, deleted or published without your yes every morning page has to show: > the facts, each with a link > the guesses, marked as guesses > what got filed or drafted overnight > the drafts in out/ still waiting for your yes the bot found them a few minutes after the upload, and the fixed return was ready to sign the same afternoon with about 90 seconds of Freedman's own time. Elon quoted it: "Grok Grok Bot can help with your taxes" connect Gmail to Grok Bot, then ask: "Turn /workspace/brain into my second brain and keep it running 1. Create raw/ (never edit), people/, projects/, out/, INDEX.md, log.md and rules.md. Every file gets a one-line summary, the date and a link to its raw source 2. Read the last 100 emails I sent through Gmail. Write me.md and voice.md with 10 rules, each with one real line of mine. Quote only lines I wrote 3. Routines in my time zone ([my time zone]): 11 PM file mail labelled Brain, 5 PM rewrite attention.md, 7:30 AM the morning page, Sundays 6 PM what I forgot, report only. Show me each first 4. Read INDEX.md and rules.md first, take fast facts from the source, add each correction to rules.md. Never send, buy, delete or publish without my yes" start with one label and one nightly routine before adding more bots keep everything in files, not in bot memory, so every bot you add later reads the same folder watch the brain at work below

this in the wrong hands. jesus. Grok Bot turned a Gmail label into a second brain that's faster and better than any human Jason Freedman (YC alum and investor) gave Grok Bot four years of tax returns, 266 unlabeled files and one assignment: "please double check my CPA's work" label an email Brain and watch it land in the right folder with a summary, the date and a link to the raw source add a second bot while keeping the same folder. Lingxi Li at SpaceXAI could manage 15 cloud agents by hand, and with Grok Bot the fleet now manages more than 200 at once each routine gets one job and runs on its own clock: → 11 PM filing copies Brain-labelled mail into raw/ and sorts it into people/ or projects/ → 5 PM attention rewrites attention.md from what you actually touched → 7:30 AM page hands you facts, guesses and the drafts waiting for your yes → Sunday 6 PM review finds what you decided and forgot a great CPA with no AI tools missed HSA contributions counted twice, four years in a row, and mortgage interest left off the 2022 return entirely Brain reopens every number at the source, never from memory, and nothing is sent, bought, deleted or published without your yes every morning page has to show: > the facts, each with a link > the guesses, marked as guesses > what got filed or drafted overnight > the drafts in out/ still waiting for your yes the bot found them a few minutes after the upload, and the fixed return was ready to sign the same afternoon with about 90 seconds of Freedman's own time. Elon quoted it: "Grok Grok Bot can help with your taxes" connect Gmail to Grok Bot, then ask: "Turn /workspace/brain into my second brain and keep it running 1. Create raw/ (never edit), people/, projects/, out/, INDEX.md, log.md and rules.md. Every file gets a one-line summary, the date and a link to its raw source 2. Read the last 100 emails I sent through Gmail. Write me.md and voice.md with 10 rules, each with one real line of mine. Quote only lines I wrote 3. Routines in my time zone ([my time zone]): 11 PM file mail labelled Brain, 5 PM rewrite attention.md, 7:30 AM the morning page, Sundays 6 PM what I forgot, report only. Show me each first 4. Read INDEX.md and rules.md first, take fast facts from the source, add each correction to rules.md. Never send, buy, delete or publish without my yes" start with one label and one nightly routine before adding more bots keep everything in files, not in bot memory, so every bot you add later reads the same folder watch the brain at work below

Argona

40,043 Aufrufe • vor 10 Tagen

i genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. you give Grok Bot one folder on its own cloud computer, feed it your emails, links and photos from your phone, and it reads them, links them, and files them into a living wiki of everything you know. it compounds like interest, the more you feed it, the smarter it gets. doesn't matter if you're a developer, a salesperson or a student, you need this the full setup: > create a bot in Grok Bot, name it Brain and add Gmail and Google Calendar in Connect apps. it runs on its own cloud computer, so it keeps working while your laptop is shut > paste the prompt from chapter 07 of my article below into its chat. one message builds the folder, the routines and the rules > it reads the last 100 emails you sent and writes voice.md, 10 rules of how you write, each with a real line of yours. no more "hope this finds you well" drafts > label any email "Brain" and every night at 11 PM it saves the original and files it on the page of that person or project > at 7:30 AM you get one page with what came in, what it drafted and what waits for your yes, ranked by the 5 projects you actually work on > correct it once and the fix goes into rules.md, which it rereads before every task. every Sunday it tells you what you decided and forgot five minutes to set up, and you never start from a blank chat again. every prompt is in the 7-step course below. or paste the whole article into Brain's chat and it builds the brain for you. bookmark this

i genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. you give Grok Bot one folder on its own cloud computer, feed it your emails, links and photos from your phone, and it reads them, links them, and files them into a living wiki of everything you know. it compounds like interest, the more you feed it, the smarter it gets. doesn't matter if you're a developer, a salesperson or a student, you need this the full setup: > create a bot in Grok Bot, name it Brain and add Gmail and Google Calendar in Connect apps. it runs on its own cloud computer, so it keeps working while your laptop is shut > paste the prompt from chapter 07 of my article below into its chat. one message builds the folder, the routines and the rules > it reads the last 100 emails you sent and writes voice.md, 10 rules of how you write, each with a real line of yours. no more "hope this finds you well" drafts > label any email "Brain" and every night at 11 PM it saves the original and files it on the page of that person or project > at 7:30 AM you get one page with what came in, what it drafted and what waits for your yes, ranked by the 5 projects you actually work on > correct it once and the fix goes into rules.md, which it rereads before every task. every Sunday it tells you what you decided and forgot five minutes to set up, and you never start from a blank chat again. every prompt is in the 7-step course below. or paste the whole article into Brain's chat and it builds the brain for you. bookmark this

Argona

73,273 Aufrufe • vor 12 Tagen

i keep telling people to build this and they nod politely and never do it... andrej karpathy posted how to fix this a while ago, and everyone just keeps working the old way the dumb thing is this... you pay to teach claude the same lessons over and over, every chat is a fresh amnesia patient, every contradiction it catches evaporates the second you close the tab, and you accept this like it's just how ai works 1. one folder is a graveyard for originals that nobody edits, another folder is claude's active memory that only claude writes to, a third folder is a two-page rulebook that keeps claude from confusing them 2. a raw file gets read the day it arrives and then it's done, claude never touches it again, everything it needed is already extracted into wiki pages with the source cited right there 3. every time claude notices your new answer clashes with your old one, it doesn't pick a side, it writes both with dates, and from then on it treats you like someone who might be wrong the raw folder is a museum... the wiki is the actual working brain full breakdown is in the article below

i keep telling people to build this and they nod politely and never do it... andrej karpathy posted how to fix this a while ago, and everyone just keeps working the old way the dumb thing is this... you pay to teach claude the same lessons over and over, every chat is a fresh amnesia patient, every contradiction it catches evaporates the second you close the tab, and you accept this like it's just how ai works 1. one folder is a graveyard for originals that nobody edits, another folder is claude's active memory that only claude writes to, a third folder is a two-page rulebook that keeps claude from confusing them 2. a raw file gets read the day it arrives and then it's done, claude never touches it again, everything it needed is already extracted into wiki pages with the source cited right there 3. every time claude notices your new answer clashes with your old one, it doesn't pick a side, it writes both with dates, and from then on it treats you like someone who might be wrong the raw folder is a museum... the wiki is the actual working brain full breakdown is in the article below

kai

32,740 Aufrufe • vor 2 Monaten

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

CyrilXBT

332,891 Aufrufe • vor 4 Monaten

Prompt engineering is where people go when they refuse to write files Karpathy's LLM Wiki gist is painfully simple: > raw sources stay untouched > the agent writes the wiki > `CLAUDE.md` or `AGENTS.md` tells it the rules > `index.md` maps the pages > `log.md` records what changed That is why a good answer should not die in chat history If the model gives you a useful comparison, summary, decision, bug explanation, or research thread, file it back into the project Use: > `wiki/topics/[topic].md` > `wiki/entities/[person-or-company].md` > `wiki/sources/[source-name].md` > `wiki/analysis/[question].md` Make the agent keep the wiki from rotting: > backlinks > summaries > contradictions > stale claims > orphan pages > missing source links For coding projects, same idea: > `CLAUDE.md`: who you are, project rules, files not to touch > `index.md`: current files and features > `log.md`: date, change, reason > saved pages: decisions you do not want to re-explain Start by saving one good answer today

Prompt engineering is where people go when they refuse to write files Karpathy's LLM Wiki gist is painfully simple: > raw sources stay untouched > the agent writes the wiki > `CLAUDE.md` or `AGENTS.md` tells it the rules > `index.md` maps the pages > `log.md` records what changed That is why a good answer should not die in chat history If the model gives you a useful comparison, summary, decision, bug explanation, or research thread, file it back into the project Use: > `wiki/topics/[topic].md` > `wiki/entities/[person-or-company].md` > `wiki/sources/[source-name].md` > `wiki/analysis/[question].md` Make the agent keep the wiki from rotting: > backlinks > summaries > contradictions > stale claims > orphan pages > missing source links For coding projects, same idea: > `CLAUDE.md`: who you are, project rules, files not to touch > `index.md`: current files and features > `log.md`: date, change, reason > saved pages: decisions you do not want to re-explain Start by saving one good answer today

Alpha Batcher

14,041 Aufrufe • vor 4 Monaten

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇

Mr. Buzzoni

18,500 Aufrufe • vor 3 Monaten

f*cking insane. you can now hire an AI chief of staff that keeps working after you close your laptop give it one rule: "find me $50,000 a month in new business". go to sleep. check your phone in the morning. a human chief of staff costs six figures a year. a Grok Bot runs on its own cloud computer with a browser, files and a terminal, and closing your laptop or your phone doesn't stop it you set the goal, it does the steps, you make the calls the rule: "find me $50,000 a month in new business. public data only. contact nobody without my yes" the night you're asking for: -> 9pm split the goal into 4 jobs and give each one a time -> 11pm pull every dental clinic in your city from public listings and cut the chains -> 1am read every site that's left and keep the best 25, each with one specific thing it noticed and where -> 2am write an opener for every one of them, send zero -> 3am build the offer on one page, no made-up results, price left blank for you -> 8am you type the price. 25 clinics × $2,000 = $50,000 a month on the table if they all say yes the blank price is the best part. an AI that guesses your price loses you the deal and it's not one bot. Grok Bots can message each other, share a group chat and hand off tasks, so one can run research while another writes and your chief of staff keeps them in line save the night as a routine and it runs again every Monday on its own it prepares the drafts. you approve them. nothing goes out without your yes someone's chief of staff is already pitching the clinics in your city the whole setup is below and free, steal it

f*cking insane. you can now hire an AI chief of staff that keeps working after you close your laptop give it one rule: "find me $50,000 a month in new business". go to sleep. check your phone in the morning. a human chief of staff costs six figures a year. a Grok Bot runs on its own cloud computer with a browser, files and a terminal, and closing your laptop or your phone doesn't stop it you set the goal, it does the steps, you make the calls the rule: "find me $50,000 a month in new business. public data only. contact nobody without my yes" the night you're asking for: -> 9pm split the goal into 4 jobs and give each one a time -> 11pm pull every dental clinic in your city from public listings and cut the chains -> 1am read every site that's left and keep the best 25, each with one specific thing it noticed and where -> 2am write an opener for every one of them, send zero -> 3am build the offer on one page, no made-up results, price left blank for you -> 8am you type the price. 25 clinics × $2,000 = $50,000 a month on the table if they all say yes the blank price is the best part. an AI that guesses your price loses you the deal and it's not one bot. Grok Bots can message each other, share a group chat and hand off tasks, so one can run research while another writes and your chief of staff keeps them in line save the night as a routine and it runs again every Monday on its own it prepares the drafts. you approve them. nothing goes out without your yes someone's chief of staff is already pitching the clinics in your city the whole setup is below and free, steal it

kiosa

20,972 Aufrufe • vor 6 Tagen

i genuinely don't understand why everyone isn't doing this yet Elon Musk posted a simple idea that hit 41 million views: stop chatting with AI. hire it. give it its own computer, its own memory, its own job that's literally what Grok Bot is. and the smartest setup right now costs $0 extra: → create a bot, name it Brain → tell it to build a private wiki of everything you know on its own computer → it sets up three folders: raw for sources, wiki for pages, and saves the whole method as a skill → drop anything into the chat: article, pdf, youtube link, screenshot. it reads it, links it, files it → put ingestion on a routine: every night it pulls what you bookmarked and files it while you sleep → ask questions across everything you've ever saved, forever your laptop stays shut. it grows anyway five minutes to set up. compounds like interest from day one Elon is already reposting people who build things with their bots. the ones who started last week have wikis, clients and his retweets six months from now they'll have a bot that read everything with them. you'll have chat history full step-by-step guide below bookmark this before the feed buries it

i genuinely don't understand why everyone isn't doing this yet Elon Musk posted a simple idea that hit 41 million views: stop chatting with AI. hire it. give it its own computer, its own memory, its own job that's literally what Grok Bot is. and the smartest setup right now costs $0 extra: → create a bot, name it Brain → tell it to build a private wiki of everything you know on its own computer → it sets up three folders: raw for sources, wiki for pages, and saves the whole method as a skill → drop anything into the chat: article, pdf, youtube link, screenshot. it reads it, links it, files it → put ingestion on a routine: every night it pulls what you bookmarked and files it while you sleep → ask questions across everything you've ever saved, forever your laptop stays shut. it grows anyway five minutes to set up. compounds like interest from day one Elon is already reposting people who build things with their bots. the ones who started last week have wikis, clients and his retweets six months from now they'll have a bot that read everything with them. you'll have chat history full step-by-step guide below bookmark this before the feed buries it

Zenith

75,427 Aufrufe • vor 6 Tagen

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓

Hanako

59,073 Aufrufe • vor 2 Monaten

I just built a self-improving second brain in Claude Code 🤯 A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time — re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: → Build 3 foundation files once: brand DNA, voice, and customer → Every skill you create reads from them automatically → Wire in live data — your ad account, competitor ads, customer reviews → A weekly routine refreshes the brain with what's actually working → Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: → The exact 3-file foundation that runs the whole system → The skill structure that makes every tool brand-aware by default → The live-data wiring that keeps it grounded in reality → The weekly self-improvement loop that keeps it sharp → The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

18,307 Aufrufe • vor 4 Monaten

This beginner guide to Karpathy's LLM Wiki is one of the most useful AI videos i've shared this year Karpathy's idea: instead of asking AI questions every time, make it build you a permanent knowledge base that grows smarter over time > drop your documents into a folder > Claude reads them and builds a structured wiki in Obsidian > every time you add a new source, Claude Sonnet updates existing pages and links new ideas > ask complex questions - Claude Opus answers from the organized wiki, not raw files it's like having a researcher who never forgets and connects dots across everything you've ever given it full setup guide is in the video above

This beginner guide to Karpathy's LLM Wiki is one of the most useful AI videos i've shared this year Karpathy's idea: instead of asking AI questions every time, make it build you a permanent knowledge base that grows smarter over time > drop your documents into a folder > Claude reads them and builds a structured wiki in Obsidian > every time you add a new source, Claude Sonnet updates existing pages and links new ideas > ask complex questions - Claude Opus answers from the organized wiki, not raw files it's like having a researcher who never forgets and connects dots across everything you've ever given it full setup guide is in the video above

Mr. Buzzoni

58,787 Aufrufe • vor 5 Monaten

GROK BOT GIVES YOU BOTS IN THE CLOUD. THIS REPO GIVES YOU YOUR OWN, ON YOUR PC. Grok Bot puts a team of bots in one chat. Alook wants that same experience with the agents you already run on your computer. in a group chat with your friends, your teammates, and their agents. it's open source, it's on GitHub, and it has passed 1,100 stars. → you pick the agent for each room → invite whoever you want → they DM the agent directly → nobody touches your machine the team of bots, but your files stay home. Open source. repo below 👇

GROK BOT GIVES YOU BOTS IN THE CLOUD. THIS REPO GIVES YOU YOUR OWN, ON YOUR PC. Grok Bot puts a team of bots in one chat. Alook wants that same experience with the agents you already run on your computer. in a group chat with your friends, your teammates, and their agents. it's open source, it's on GitHub, and it has passed 1,100 stars. → you pick the agent for each room → invite whoever you want → they DM the agent directly → nobody touches your machine the team of bots, but your files stay home. Open source. repo below 👇

matt

38,971 Aufrufe • vor 18 Tagen

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,804 Aufrufe • vor 4 Monaten

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,643 Aufrufe • vor 4 Monaten

Most people use Claude Code like a chatbot, then wonder why it forgets everything by Tuesday. The ones quietly building $10K AI workflows give it a second brain instead, and it’s free. It’s called Obsidian. You download it, point it at one folder on your computer, and that folder becomes a vault. Every note inside it is now something Claude Code can read end to end. Open Claude in that folder and it’s connected, that simple. The trick isn’t the tool, it’s the map. 3 folders, that’s the whole system. Raw, you dump everything here. Notes, transcripts, screenshots, half thoughts, zero structure. Wiki, Claude reads the raw pile and writes clean Wikipedia style articles about it, structured, searchable, permanent. Output, when you want a deliverable, a PDF, a slide deck, a script, it pulls from the wiki and ships it. Most people skip the wiki layer and feed Claude a junk drawer of 400 files, then blame the model when the answers are garbage. The model isn’t the problem, your folder is. Give it a path it can follow and it finds anything in 1 second, give it chaos and it guesses. You don’t even have to design the structure yourself. Open the vault, tell Claude to build a file system that fits your work, and watch it organize your entire brain in one prompt. Free tool, 3 folders, a second brain that compounds while you sleep. The people falling behind are still copy pasting into a chat window.

Most people use Claude Code like a chatbot, then wonder why it forgets everything by Tuesday. The ones quietly building $10K AI workflows give it a second brain instead, and it’s free. It’s called Obsidian. You download it, point it at one folder on your computer, and that folder becomes a vault. Every note inside it is now something Claude Code can read end to end. Open Claude in that folder and it’s connected, that simple. The trick isn’t the tool, it’s the map. 3 folders, that’s the whole system. Raw, you dump everything here. Notes, transcripts, screenshots, half thoughts, zero structure. Wiki, Claude reads the raw pile and writes clean Wikipedia style articles about it, structured, searchable, permanent. Output, when you want a deliverable, a PDF, a slide deck, a script, it pulls from the wiki and ships it. Most people skip the wiki layer and feed Claude a junk drawer of 400 files, then blame the model when the answers are garbage. The model isn’t the problem, your folder is. Give it a path it can follow and it finds anything in 1 second, give it chaos and it guesses. You don’t even have to design the structure yourself. Open the vault, tell Claude to build a file system that fits your work, and watch it organize your entire brain in one prompt. Free tool, 3 folders, a second brain that compounds while you sleep. The people falling behind are still copy pasting into a chat window.

West Lord

32,845 Aufrufe • vor 4 Monaten

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.

MOST "SECOND BRAINS" ARE JUST FOLDERS YOU FEEL GUILTY ABOUT. HERE'S HOW CLAUDE TURNS ONE INTO A BRAIN THAT ANSWERS YOU. that clip is the build: obsidian plus claude, structured like a filing cabinet. three drawers, one job each: raw: everything you dump in, docs, sheets, pdfs, transcripts, untouched new knowledge: what claude distills, links and rewrites into clean notes and the connections between them, drawn automatically the part most note apps miss: you are not the librarian. you drop the raw in. claude reads it once, files it, links it to what you already had, and updates the index. then you never dig through the raw pile again. you ask the brain, and it answers from the clean layer with sources. that graph on screen isn't decoration. every line is a connection you didn't have to make by hand. no re-reading the same pdf, no notes you wrote once and never opened, no app that guilts you for not organizing. the uncomfortable part isn't that note apps are messy. it's that a second brain was never about saving more, it was about something rereading you after you stopped. follow RetroChainer for systems that keep thinking after you close the tab, and bookmark this before your notes turn into another graveyard.

RetroChainer

13,775 Aufrufe • vor 2 Monaten

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.

Karpathy gave 100,000 people the LLM Wiki idea. 1 guy actually built it into a Claude + Obsidian brain that never forgets you. Every AI tool forgets you the second you close the tab. ChatGPT, Claude, Codex. All gone. He killed that. A shared memory layer your AI builds and maintains on its own. 3 layers. Raw, Wiki, Schema. You drop a source, Claude reads it, pulls the concepts, links them, cites the original, never touches your raw notes. Scales to 1,000s of notes without breaking. Then it goes deeper. An agentic firewall locks agents out of your other vaults. A local model running free and private, zero cloud. 2 videos walk through it all. 1 on why. 1 on the build, start to finish. Most people will keep pasting the same context into 6 tabs for the next 3 years. Build it once. Never explain yourself to a model again.

West Lord

75,208 Aufrufe • vor 4 Monaten