Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself...

0xDepressionn's profile picture

Dep

46,183 subscribers

20,909 görüntüleme • 1 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.
0:37

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

shmidt

16,085 görüntüleme • 1 ay önce

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.
31:18

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.

Raytar

28,046 görüntüleme • 1 ay önce

Сreator of Claude Code: BORIS CHERNY, WHO BUILT CLAUDE CODE, SAID IT PLAINLY." I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops. "He is not typing anymore. He runs loops that write the code for him. That is the shift most people miss. Not a better prompt. A loop that keeps running while you are gone.People sell $500 courses on this. The person who built the tool said it for free. The exact setup is in the article below.Bookmark this. Follow CyrilXBT
18:08

Сreator of Claude Code: BORIS CHERNY, WHO BUILT CLAUDE CODE, SAID IT PLAINLY." I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops. "He is not typing anymore. He runs loops that write the code for him. That is the shift most people miss. Not a better prompt. A loop that keeps running while you are gone.People sell $500 courses on this. The person who built the tool said it for free. The exact setup is in the article below.Bookmark this. Follow CyrilXBT

CyrilXBT

38,748 görüntüleme • 1 ay önce

HOW TO USE AI LOOPS TO RUN YOUR BUSINESS 24/7 A lot has been written about loop engineering for building products. Almost nothing about using loops to run the business itself. That's the bigger idea. A loop is when you give an agent a goal, a way to check its own work, and permission to keep trying until it hits that goal. Build. Verify. Repeat. Stop when the condition is met. Here's what it looks like in practice: 1/SEO loop You're position 30 for a term you want. The loop runs once a month, makes changes, checks where you rank, and keeps pushing until you're on page one. This is running in production right now on Inbox Zero. 2/Ads loop You're spending $100 a day and losing money. The loop tests creative, checks profitability, kills what fails, and keeps going until the account is in the black. 3/Eval loop Your AI feature is only 88% accurate. The loop keeps adjusting the prompt and swapping the model until it passes 90%. 4/LLM visibility loop People search in ChatGPT now, not just Google. Same loop, new scoreboard. Are we the answer or not? The whole thing hinges on one thing: a metric that comes back black and white. Where do I rank? Did it hit profitability? Did the evals pass? Give an agent that scoreboard and it runs for months. Loops used to run for 30 minutes. These run for a year. Take a step, sleep, wake up next month, take another one. You're basically hiring an agency that never sleeps, gets paid in tokens instead of invoices, and undoes its own mistakes when the number goes down. Full episode on The Startup Ideas Podcast (SIP) 🧃 watch
39:43

HOW TO USE AI LOOPS TO RUN YOUR BUSINESS 24/7 A lot has been written about loop engineering for building products. Almost nothing about using loops to run the business itself. That's the bigger idea. A loop is when you give an agent a goal, a way to check its own work, and permission to keep trying until it hits that goal. Build. Verify. Repeat. Stop when the condition is met. Here's what it looks like in practice: 1/SEO loop You're position 30 for a term you want. The loop runs once a month, makes changes, checks where you rank, and keeps pushing until you're on page one. This is running in production right now on Inbox Zero. 2/Ads loop You're spending $100 a day and losing money. The loop tests creative, checks profitability, kills what fails, and keeps going until the account is in the black. 3/Eval loop Your AI feature is only 88% accurate. The loop keeps adjusting the prompt and swapping the model until it passes 90%. 4/LLM visibility loop People search in ChatGPT now, not just Google. Same loop, new scoreboard. Are we the answer or not? The whole thing hinges on one thing: a metric that comes back black and white. Where do I rank? Did it hit profitability? Did the evals pass? Give an agent that scoreboard and it runs for months. Loops used to run for 30 minutes. These run for a year. Take a step, sleep, wake up next month, take another one. You're basically hiring an agency that never sleeps, gets paid in tokens instead of invoices, and undoes its own mistakes when the number goes down. Full episode on The Startup Ideas Podcast (SIP) 🧃 watch

GREG ISENBERG

82,335 görüntüleme • 1 ay önce

Claude Code creator Boris Cherny: "Verification is the single most important part of closed-loop development" "Companies underinvest in it, and that is the biggest mistake" In a 26-minute talk, Boris breaks down real AI coding loops with Spotify's Chief Engineer: 00:00 - Closed-loop development 08:33 - Why one-shot code generation fails 10:02 - Agentic verifier and PR success rate 12:00 - Verification loops without humans in the loop 14:00 - Tests, skills, CLAUDE.md, and MCP as the loop infrastructure 20:11 - Why consistent codebases make agents work better This one video is worth more than 100 Claude coding setup tutorials Bookmark and watch it today Then read the full guide on loop engineering below
26:31

Claude Code creator Boris Cherny: "Verification is the single most important part of closed-loop development" "Companies underinvest in it, and that is the biggest mistake" In a 26-minute talk, Boris breaks down real AI coding loops with Spotify's Chief Engineer: 00:00 - Closed-loop development 08:33 - Why one-shot code generation fails 10:02 - Agentic verifier and PR success rate 12:00 - Verification loops without humans in the loop 14:00 - Tests, skills, CLAUDE.md, and MCP as the loop infrastructure 20:11 - Why consistent codebases make agents work better This one video is worth more than 100 Claude coding setup tutorials Bookmark and watch it today Then read the full guide on loop engineering below

rari

73,045 görüntüleme • 1 ay önce

THE GUY RUNNING CLAUDE CODE AT ANTHROPIC JUST SAID HE DOESN’T PROMPT AI ANYMORE. He writes loops. That’s a huge difference. A prompt tells Claude what to do once. A loop gives Claude a goal. Then Claude keeps checking its own work… Finding mistakes. Writing its next prompt. Trying again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below
1:36

THE GUY RUNNING CLAUDE CODE AT ANTHROPIC JUST SAID HE DOESN’T PROMPT AI ANYMORE. He writes loops. That’s a huge difference. A prompt tells Claude what to do once. A loop gives Claude a goal. Then Claude keeps checking its own work… Finding mistakes. Writing its next prompt. Trying again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below

kiosa

16,808 görüntüleme • 1 ay önce

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.
0:31

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,576 görüntüleme • 22 gün önce

Anthropic engineer: "Over 90% of Anthropic engineers use a self-improving agentic loop for coding. The key is to close the loop: give the agent a way to verify and improve its own work" In this 12-minute talk, an Anthropic engineer explains how to build an agent that continuously improves itself. Claude + routines + loops + CLAUDE.md - that's the foundation. Skip Netflix tonight. Save this post!
12:06

Anthropic engineer: "Over 90% of Anthropic engineers use a self-improving agentic loop for coding. The key is to close the loop: give the agent a way to verify and improve its own work" In this 12-minute talk, an Anthropic engineer explains how to build an agent that continuously improves itself. Claude + routines + loops + CLAUDE.md - that's the foundation. Skip Netflix tonight. Save this post!

unicode

62,153 görüntüleme • 1 ay önce

There are two types of engineers in 2026 The first opens his laptop in the morning, writes a prompt, waits, reads the diff, fixes it, repeats The second opens his phone, checks what shipped while he was asleep Different answer to one question: who is the loop? The first engineer is the loop, he starts the agent, reviews the output, decides what's next, the moment he steps away it stops The second engineer built the system that is the loop instead of him, PR review, flaky tests, CI triage, all running without him, he just reads the report What stops most people isn't complexity It's that they never noticed they are the bottleneck Full guide to building the system that runs without you below
1:04

There are two types of engineers in 2026 The first opens his laptop in the morning, writes a prompt, waits, reads the diff, fixes it, repeats The second opens his phone, checks what shipped while he was asleep Different answer to one question: who is the loop? The first engineer is the loop, he starts the agent, reviews the output, decides what's next, the moment he steps away it stops The second engineer built the system that is the loop instead of him, PR review, flaky tests, CI triage, all running without him, he just reads the report What stops most people isn't complexity It's that they never noticed they are the bottleneck Full guide to building the system that runs without you below

plutos

14,653 görüntüleme • 2 ay önce

Peter Steinberger, creator of OpenClaw, on why AI agents still produce "slop" without human taste in the loop: "You can create code and run all night and then you have like the ultimate slop because what those agents don't really do yet is have taste." Peter is direct: raw capability without direction still produces mediocre output. "They are spiky smart and they're really good at things, but if you don't navigate them well, if you don't have a vision of what you're going to build, it's still going to be slop. If you don't ask the right questions, it's still going to be slop." Great AI-assisted work is defined by the human guiding it. Peter Steinberger 🦞 describes his own creative process when starting a new project: "When I start a project, I have like this very rough idea what it could be. And as I play with it and feel it, my vision gets more clear. I try out things, some things don't work, and I evolve my idea into what it will become." Most people skip this part entirely, front-loading everything into a single prompt and wondering why the result feels hollow. "My next prompt depends on what I see and feel and think about the current state of the project." Each step informs the next. The work itself is the feedback loop. "But if you try to put everything into a spec up front, you miss this kind of human-machine loop. And then I don't know how something good can come out without having feelings in the loop — almost like taste." The agentic trap is what happens when you remove yourself from the process too early.
1:09

Peter Steinberger, creator of OpenClaw, on why AI agents still produce "slop" without human taste in the loop: "You can create code and run all night and then you have like the ultimate slop because what those agents don't really do yet is have taste." Peter is direct: raw capability without direction still produces mediocre output. "They are spiky smart and they're really good at things, but if you don't navigate them well, if you don't have a vision of what you're going to build, it's still going to be slop. If you don't ask the right questions, it's still going to be slop." Great AI-assisted work is defined by the human guiding it. Peter Steinberger 🦞 describes his own creative process when starting a new project: "When I start a project, I have like this very rough idea what it could be. And as I play with it and feel it, my vision gets more clear. I try out things, some things don't work, and I evolve my idea into what it will become." Most people skip this part entirely, front-loading everything into a single prompt and wondering why the result feels hollow. "My next prompt depends on what I see and feel and think about the current state of the project." Each step informs the next. The work itself is the feedback loop. "But if you try to put everything into a spec up front, you miss this kind of human-machine loop. And then I don't know how something good can come out without having feelings in the loop — almost like taste." The agentic trap is what happens when you remove yourself from the process too early.

Big Brain AI

488,749 görüntüleme • 4 ay önce

ANTHROPIC LEAD ENGINEER MAKING $2.3M/YEAR JUST LEAKED A 12-PAGE DOCUMENT - AND GOT FIRED 15 MINUTES AFTER PUBLISHING most developers build loops - but almost every loop breaks in one of five ways, and each failure has a symptom visible from the outside without reading a single line of code > Blind loop - the agent waits for a human to hand it work every morning - automating execution but not discovery > Tangled loop - parallel agents share one directory and overwrite each other parallelism that destroys instead of multiplies > Nodding loop - the agent grades its own work and approves it every time a loop that has never said no to itself is broken > Amnesiac loop - results live only in the context window every morning the system wakes up with no memory of yesterday > Manual loop - no trigger a human presses the button to start it that is not a loop that is a script waiting for a person a real loop finds its own work - remembers what it did has something that can say no never lets two agents touch the same file and fires itself on a timer remove any one of the five - and the loop either breaks or never starts 12 pages that changed how I build agentic systems today
0:50

ANTHROPIC LEAD ENGINEER MAKING $2.3M/YEAR JUST LEAKED A 12-PAGE DOCUMENT - AND GOT FIRED 15 MINUTES AFTER PUBLISHING most developers build loops - but almost every loop breaks in one of five ways, and each failure has a symptom visible from the outside without reading a single line of code > Blind loop - the agent waits for a human to hand it work every morning - automating execution but not discovery > Tangled loop - parallel agents share one directory and overwrite each other parallelism that destroys instead of multiplies > Nodding loop - the agent grades its own work and approves it every time a loop that has never said no to itself is broken > Amnesiac loop - results live only in the context window every morning the system wakes up with no memory of yesterday > Manual loop - no trigger a human presses the button to start it that is not a loop that is a script waiting for a person a real loop finds its own work - remembers what it did has something that can say no never lets two agents touch the same file and fires itself on a timer remove any one of the five - and the loop either breaks or never starts 12 pages that changed how I build agentic systems today

Sprytix

153,575 görüntüleme • 1 ay önce

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below
36:48

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below

Anatoli Kopadze

28,042 görüntüleme • 1 ay önce

Terrence McKenna in an interview in 1998: "I think it's just going to get weirder and weirder and weirder, and finally, it's going to be so weird that people will have to talk about how weird it is. [...] This is what it's like when a species prepares to depart for the stars. You don't depart for the stars under calm and orderly conditions. It's a fire in a madhouse, and that's what we have - the fire in the madhouse at the end of time. This is what it's like when a species prepares to move on to the next dimension."
4:39

Terrence McKenna in an interview in 1998: "I think it's just going to get weirder and weirder and weirder, and finally, it's going to be so weird that people will have to talk about how weird it is. [...] This is what it's like when a species prepares to depart for the stars. You don't depart for the stars under calm and orderly conditions. It's a fire in a madhouse, and that's what we have - the fire in the madhouse at the end of time. This is what it's like when a species prepares to move on to the next dimension."

𓆝𓆜𓆞𓆢

26,389 görüntüleme • 1 yıl önce

Right now, most developers are still doing the job AI should be doing. Assign a task. Wait. Review the result. Fix it. Repeat. You're not building with AI. You're babysitting it. The shift happening now is much bigger than better coding agents. It's loop engineering. Instead of managing every AI agent yourself, you build a system that manages them for you. One loop assigns the work. Another checks the output. A third retries failures. Everything keeps moving without waiting for your next prompt. Your job doesn't disappear. It changes. You stop acting like a project manager... ...and start designing the system that manages the entire team. That's exactly the transition I break down in the article below.
1:41

Right now, most developers are still doing the job AI should be doing. Assign a task. Wait. Review the result. Fix it. Repeat. You're not building with AI. You're babysitting it. The shift happening now is much bigger than better coding agents. It's loop engineering. Instead of managing every AI agent yourself, you build a system that manages them for you. One loop assigns the work. Another checks the output. A third retries failures. Everything keeps moving without waiting for your next prompt. Your job doesn't disappear. It changes. You stop acting like a project manager... ...and start designing the system that manages the entire team. That's exactly the transition I break down in the article below.

Pure

11,257 görüntüleme • 1 ay önce

While AI timeline argues about loop engineering, a 20-year-old student in Shenzhen built the biggest loop anyone's aimed at money: 300 agents, one brain, $1,200 -> 395,000. Not a prompt. Not a bot. A loop that runs the whole job on its own - and never asks him a thing. No fund. No backers. Just a laptop, a dorm room, and a bet that a swarm beats a genius. His wallet: The smartest single model still works one step at a time. His loop moves in 300 directions at once - and never checks in with him. Claude Opus 4.8 runs the floor as the brain. 300 agents are the hands. One loop ties them together: > Decompose - Opus breaks the market into targets > Dispatch - 300 agents scatter across them at once > Execute - thousands of reads in a single pass, not one by one > Review - Opus grades every edge before a cent moves The hands find. The brain judges. The loop learns what failed and runs again, tighter each time. One daily loss cap, and it shuts itself down. It's not a bot you babysit. It's a loop that runs the whole desk. Everyone's just learning to run one loop. He runs 300 in one. The edge was never the genius model - it's the size of the loop, and the brain in charge of it. Save this - the full 300-agent loop is laid out above, start to finish. You'll want it when you build your own. 300 agents are looping right now, hunting the markets everyone skips. Two clicks and their trades land in your wallet too:
0:53

While AI timeline argues about loop engineering, a 20-year-old student in Shenzhen built the biggest loop anyone's aimed at money: 300 agents, one brain, $1,200 -> 395,000. Not a prompt. Not a bot. A loop that runs the whole job on its own - and never asks him a thing. No fund. No backers. Just a laptop, a dorm room, and a bet that a swarm beats a genius. His wallet: The smartest single model still works one step at a time. His loop moves in 300 directions at once - and never checks in with him. Claude Opus 4.8 runs the floor as the brain. 300 agents are the hands. One loop ties them together: > Decompose - Opus breaks the market into targets > Dispatch - 300 agents scatter across them at once > Execute - thousands of reads in a single pass, not one by one > Review - Opus grades every edge before a cent moves The hands find. The brain judges. The loop learns what failed and runs again, tighter each time. One daily loss cap, and it shuts itself down. It's not a bot you babysit. It's a loop that runs the whole desk. Everyone's just learning to run one loop. He runs 300 in one. The edge was never the genius model - it's the size of the loop, and the brain in charge of it. Save this - the full 300-agent loop is laid out above, start to finish. You'll want it when you build your own. 300 agents are looping right now, hunting the markets everyone skips. Two clicks and their trades land in your wallet too:

cvxv666

53,163 görüntüleme • 1 ay önce

The guy who kicked off the entire "loop engineering" wave Peter Steinberger: "You shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agents." One post. 6.5M views in a week. In this talk he walks the real stack: the agent loop, a verifier that fails its own work and retries, and a loop that rewrites the agent while he sleeps. Worth more than any $500 vibe-coding course. Watch it, then read the full breakdown of the 4 loops below.
17:30

The guy who kicked off the entire "loop engineering" wave Peter Steinberger: "You shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agents." One post. 6.5M views in a week. In this talk he walks the real stack: the agent loop, a verifier that fails its own work and retries, and a loop that rewrites the agent while he sleeps. Worth more than any $500 vibe-coding course. Watch it, then read the full breakdown of the 4 loops below.

dunik

219,932 görüntüleme • 1 ay önce

Anthropic engineer: "The fastest way to make an agent better isn't a smarter model, it's the right loop and graph around it." In 60 minutes she breaks down how Anthropic engineers use Claude Code, build agents that catch their own mistakes and improve with every run. This beats any $500 agentic engineering course you can find. Watch it, then read the full guide on loops and graphs below.
59:59

Anthropic engineer: "The fastest way to make an agent better isn't a smarter model, it's the right loop and graph around it." In 60 minutes she breaks down how Anthropic engineers use Claude Code, build agents that catch their own mistakes and improve with every run. This beats any $500 agentic engineering course you can find. Watch it, then read the full guide on loops and graphs below.

Anatoli Kopadze

122,265 görüntüleme • 4 gün önce

Boris Cherny (creator of Claude Code, Anthropic): "My entire CLAUDE.md is two lines. With every new model you need less instruction, not more, most people are over-engineering the one thing that should stay tiny." in a 7-minute interview, Boris Cherny breaks down why the smallest AI-coding setup wins, and the one moment you should delete your config and start from scratch most engineers do the opposite: they pile on rules, build scaffolding around the model… then the next model ships and makes all of it useless. what he actually keeps in those two lines, and why he tells his team to throw the rest away. Watch the talk, then read the article below. That’s worth more than a $800 course on agent engineering.
7:13

Boris Cherny (creator of Claude Code, Anthropic): "My entire CLAUDE.md is two lines. With every new model you need less instruction, not more, most people are over-engineering the one thing that should stay tiny." in a 7-minute interview, Boris Cherny breaks down why the smallest AI-coding setup wins, and the one moment you should delete your config and start from scratch most engineers do the opposite: they pile on rules, build scaffolding around the model… then the next model ships and makes all of it useless. what he actually keeps in those two lines, and why he tells his team to throw the rest away. Watch the talk, then read the article below. That’s worth more than a $800 course on agent engineering.

Prometheus

238,143 görüntüleme • 2 ay önce

Anthropic engineers just showed how they build a full app from scratch, using a loop of agents 40 minutes from the team behind Claude Code they used three agents: one to plan, one to build, one to judge, cycling until the app actually works the winners won't have the smartest model, they'll have the best loop watch it, then read the full guide on how to actually use loops below
39:36

Anthropic engineers just showed how they build a full app from scratch, using a loop of agents 40 minutes from the team behind Claude Code they used three agents: one to plan, one to build, one to judge, cycling until the app actually works the winners won't have the smartest model, they'll have the best loop watch it, then read the full guide on how to actually use loops below

Kyronis

11,121 görüntüleme • 1 ay önce

ONE PROMPT AND ONE BUTTON NOW BUILDS A FULL SYSTEM, DATABASE, BACKEND, AND FRONTEND INCLUDED Most people still picture AI as something you ask questions to, then copy the answer into your own code by hand. A builder wired Claude into Obsidian through MCP instead, so a single written prompt becomes the actual spec for the system. Claude breaks that prompt into database schema, UI components, and API endpoints on its own, then writes, runs, and fixes the code until it actually works. MCP is what makes this possible, it lets the agent see the filesystem, installed packages, and running services before it starts building anything. The output isn't a code snippet sitting in a chat window, it's a live local app running on its own server, ready to open in a browser. What used to need a backend developer, a DevOps engineer, and two weeks now finishes in under fifteen minutes. See the full architecture and prompt structure below👇
0:21

ONE PROMPT AND ONE BUTTON NOW BUILDS A FULL SYSTEM, DATABASE, BACKEND, AND FRONTEND INCLUDED Most people still picture AI as something you ask questions to, then copy the answer into your own code by hand. A builder wired Claude into Obsidian through MCP instead, so a single written prompt becomes the actual spec for the system. Claude breaks that prompt into database schema, UI components, and API endpoints on its own, then writes, runs, and fixes the code until it actually works. MCP is what makes this possible, it lets the agent see the filesystem, installed packages, and running services before it starts building anything. The output isn't a code snippet sitting in a chat window, it's a live local app running on its own server, ready to open in a browser. What used to need a backend developer, a DevOps engineer, and two weeks now finishes in under fifteen minutes. See the full architecture and prompt structure below👇

wast3

20,348 görüntüleme • 1 ay önce