Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

THIS GUY BUILT A REAL JARVIS THAT TURNS HIS IDEAS INTO FINISHED PROJECTS ON ITS OWN, AND HE JUST SHOWED HOW THE WHOLE THING WORKS The whole system runs on one clean split he calls a blood-brain barrier. The second brain, his Obsidian vault, is only for things that...

87,075 Aufrufe • vor 1 Monat •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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,186 Aufrufe • vor 1 Monat

Obsidian + Claude Code is how Andrej Karpathy turns 15 years of notes into a brain that works while he sleeps. The method behind it costs $0 and takes 5 minutes a day and it outlived every productivity app since 2011. Every idea, link, and half-thought gets appended to the top of a single note, with no sorting, no folders, no tags. Once a week he scrolls through, and anything that still matters gets copied back to the top. Weak ideas sink. Strong ideas resurface 5, 10, 20 times and by the 20th pass your brain has already wired them into everything else you know. Repetition as a filter. That's the whole system. Now the 2026 upgrade almost nobody is running: Drop that note into an Obsidian vault and open the folder with Claude Code not the chat app, the terminal agent that reads files. 3 commands change everything: read my last 30 days of notes and find the 3 ideas I keep circling without acting on link every note mentioning this project into a CLAUDE.md of what I actually believe about it draft this week's post from the idea that resurfaced most Claude Code doesn't search your vault it walks it, follows the wikilinks, and hands you the patterns you were too close to see. Karpathy method filters the signal, Obsidian stores it, Claude Code compounds it. One is a habit, one is a folder, one is $20 a month together they're the closest thing to a second brain that thinks back. Most people collect notes for 10 years and never read them once. His notes read him.

Spike 1%

12,291 Aufrufe • vor 15 Tagen

This guy replaced an $8,000 survey crew with one drone and a pipeline on Claude Code that digitizes a whole site in a single trip. Inside it is not one drone but a whole pipeline of 5 modules on Claude Code each with its own job all answering to a single orchestrator. And he built them himself with no team. He draws one line on the map from the controller and the whole site starts turning into data at once. Pilot flies the DJI Matrice 350 RTK along the route and reaches where a crew drags tripods: the parking lot and the roofs and the grading. Scanner on the Zenmuse L2 records the geometry with a laser down to the centimeter. Builder in DJI Terra stitches the point cloud into a digital twin. Analyst on Claude builds what the client needs out of the finished model: a volume report and a progress diff and a tour behind a link. Mobile lives in his iPhone and hands the developer a link to the model while he drives to the next site. The site is ready as a file in about an hour and the developer rotates it in the browser himself and measures distances. No crew. No tripods. No week on site. Just him and a pickup and a drone and one API key. The whole processing pipeline lives in a folder at /Users/dev/site-capture. But he did not stop at a one time scan. The pipeline raises him by voice only when a flight misses a patch or when a sag on site goes past tolerance. And this is not made up: the DJI Matrice 350 RTK and the Zenmuse L2 are off the shelf enterprise hardware. The specs are one search away and the L2 really does write around 240,000 points per second. A crew for the same job charges $8,000 and three trips plus a week of desk work. His cost is tokens and subscriptions: one battery charge per flight and around $300 a month to host the finished models. In the end he draws one line on the map and an operator that does not exist scans the site and calculates the volumes and builds the report while he never leaves his truck. There is a huge market of everyone who needs to measure construction sites and warehouses and roofs and parking lots over and over while they still send out a photographer with a camera and wait a week. And he built this whole pipeline himself: one drone and one scanner and Claude Code that turns a flight into a file the developer pays for.

Blaze

10,681 Aufrufe • vor 1 Monat

Obsidian just became the most dangerous folder on your computer, and Andrej Karpathy predicted it with 1 markdown file. His method is called append-and-review. He described it years ago and almost nobody listened: 1 single note, every thought appended to the top, reviewed on random scrolls. No tags, no folders, no Notion dashboards with 40 linked databases. The problem was always the same the note remembers, but it can't act. That changed the moment people pointed Claude Code at an Obsidian vault. Here's the setup that's quietly spreading: Part 1 — The vault becomes a database. Obsidian stores everything as plain markdown on your disk, which means Claude Code can read it like a codebase. You open a terminal inside the vault folder and your 2,000 notes turn into queryable memory. Part 2 — The CLAUDEmd file becomes the brain stem. One file at the root tells the agent who you are, what you're building, and how your notes are structured. From that point every session starts with full context instead of a blank chat window. Part 3 — Karpathy append log becomes fuel. You dump raw thoughts all day ideas, links, half-sentences. Then 1 command at night: review today's appends, extract action items, draft the 3 posts hiding in there, link them to existing notes. The messy log goes in, structured output comes out, and the vault rewrites itself while you sleep. Part 4 — Agents start living in your notes. People are running weekly reviews, content calendars, even market research as scheduled Claude Code runs over their vault. Your second brain stops being a graveyard of highlights and starts shipping. The honest math: setup takes about 90 minutes, the first week feels like overkill, and by day 30 you're sitting on a system where every note you've written in 5 years is working for you instead of rotting in a folder. Notion needed a server, a subscription and your data on someone else's machine. Obsidian needed a text file and now the text file has an employee.

Spike 1%

58,428 Aufrufe • vor 16 Tagen

The smartest man in AI just exposed the whole AGI narrative as a LIE. And he used a physics problem from 1905 to prove it. His name is Demis Hassabis. He runs Google DeepMind, and won the Nobel Prize for using AI to crack a problem in biology that had stumped scientists for 50 years. Almost nobody in this industry has a track record like his. He went on the NothingButTech podcast and called out the biggest lie in AI right now: Right now the loudest voices in AI are telling you that AGI is basically here. OpenAI has literally defined AGI as a system that can outperform humans at most "economically valuable work." In other words, if it replaces enough jobs, we have arrived. Hassabis thinks that bar is a joke. He said real general intelligence has to do what the human brain can do, because the brain is the only proof we have that this kind of intelligence is even possible. He called that "a higher bar than just being able to do some useful economic work," which is about as close as a polite British Nobel laureate gets to calling his rivals out. Then he gave the actual test: Today's AI has read everything humans have ever written, including the theory of relativity. So when it explains relativity back to you, it's repeating an answer that already exists. That's not intelligence. So Hassabis proposed a test that makes memorization impossible. Train an AI on only what humanity knew in 1901, four years BEFORE Einstein published relativity. Then ask it to come up with relativity on its own. It can't look up the answer, because in 1901 the answer doesn't exist yet. The only way to pass is to do what Einstein actually did: Take the same physics everyone else had and reason its way to an idea no human had ever had. Hassabis says not a single AI today can, no matter how much it has memorized. Which means what we keep calling "almost AGI" is really just the best librarian in history. It can find any answer that already exists but it cannot create one that doesn't. His second version is even sharper: AlphaGo, the system his own team built, famously invented a brand new move that no human had played in 2,000 years of the game. Everyone called it genius but Hassabis says that still is not the bar. The real test is not whether an AI can invent a new move inside Go, it is whether an AI could INVENT a game as deep and as beautiful as Go in the first place. No model that exists today can do it. The people telling you AGI has already arrived are the same people raising hundreds of billions of dollars on that exact promise. The valuations only work if the finish line is right in front of us. So the finish line keeps getting dragged closer, and AGI keeps getting quietly redefined down to "does useful work," until the products they already sell happen to qualify. Hassabis has nothing to prove and nothing to sell you. He already won the Nobel, and he is telling you the machines still cannot do the one thing that would make them genuinely intelligent, which is have a truly original idea. To be fair to him, he is not a pessimist about it. He believes real AGI IS coming, and he is spending his life building it. He just refuses to pretend it is already sitting in your phone. So the next time a founder tells you AGI is months away, remember that the one man in the room with a Nobel Prize built his test around Einstein, and admitted that nothing we have made can pass it. What do you think?

Ricardo

1,285,723 Aufrufe • vor 1 Monat

This guy runs his entire marketing department out of folders and markdown files. No code or crazy automations. He calls it CMOHQ, it works with any AI (Claude, ChatGPT, Hermes, Codex), and he sells the whole thing as a zip file. He went 3 weeks without opening his laptop and the business kept running. Justin Brooke ❤️‍🔥 is back on the pod to walk us through the entire system. Here's what I learned: 1. The whole OS is folders and markdown files. He tried n8n, LangChain, and CrewAI. Too technical for a copywriter. 2. One HQ folder for who you are. One folder per brand with intelligence, departments, and metrics inside. Say "work in the FaithFunnels brand" and Claude switches context. 3. He built the finance folder from a YouTube transcript. It ingests ThriveCart, Kit, Google Ads, and Zeni exports and auto-generates max CPA, spend ceilings, and dashboards. 4. Build it in iCloud, not on a Mac Mini. It's just text files. Phone, laptop, office, same brain. 5. Nothing skips the pipeline. Pope mentions "digital sobriety," Claude writes the article, he approves, it publishes to Ghost via MCP with an ElevenLabs audio version. 6. Reporting is wired in through MCPs. Kit, Google Analytics, Microsoft Clarity. Clicks to leads to sales, plus a monthly P&L drop. 7. He uses Claude Cowork, not Claude Code. 90% of the features, and his work is mostly writing anyway. 8. Start with Jobs To Be Done. Every job becomes a folder. Every folder gets instructions. 9. Delivery is the product. The zip holds an ops manual and an installer.md that interviews the buyer and builds their system. Zero onboarding calls. 10. If they want to build it themselves, they're not your customer. Millionaires look at the system and say "can I just pay you?" His 2 key takeaways: 1. Every agent needs three things: memory, instructions, and tools. Get those right and you can replicate any process in any business. 2. Stop doing sales calls on the fly. Run a slide deck, tweak one slide per call, and by call five it's dialed in and trainable. That's how you get out of sales. Justin has been marketing for 20 years and this is the simplest AI operating system I've seen. Go follow Justin Brooke ❤️‍🔥 Full video below. (Also available on the Build With AI podcast wherever you get your pods)

Corey Ganim

13,753 Aufrufe • vor 26 Tagen