Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

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:show more

cvxv666

11,121 subscribers

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

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

A 20-year-old in Shenzhen owns a company that turned $1,200 into $395,000. Its workforce is 300 AI agents. Its CEO is also an AI. Human employees: zero. The entire org chart: > CEO - Claude Opus 4.8. Sets the goal, vetoes every weak trade. > Workforce - 300 agents. They read the order book, the news, every Bitcoin market at once. > Risk officer - a hard daily loss cap. Shuts the whole floor the second it's hit. > Payroll: $0. Meetings: 0. Days off: 0. > HQ: a dorm room. It runs as one loop - the agents propose, the CEO disposes, the survivors trade, repeat. He just owns the place. Save this full loop pipeline is in the post below.

A 20-year-old in Shenzhen owns a company that turned $1,200 into $395,000. Its workforce is 300 AI agents. Its CEO is also an AI. Human employees: zero. The entire org chart: > CEO - Claude Opus 4.8. Sets the goal, vetoes every weak trade. > Workforce - 300 agents. They read the order book, the news, every Bitcoin market at once. > Risk officer - a hard daily loss cap. Shuts the whole floor the second it's hit. > Payroll: $0. Meetings: 0. Days off: 0. > HQ: a dorm room. It runs as one loop - the agents propose, the CEO disposes, the survivors trade, repeat. He just owns the place. Save this full loop pipeline is in the post below.

cvxv666

29,425 görüntüleme • 1 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

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

A 21-YEAR-OLD FROM CHINA RUNS 300 AI AGENTS AT ONCE. THE PART THAT MATTERS ISN'T THE SPEED, IT'S THAT NONE OF THEM CAN LIE TO HIM he opens the dashboard and shows the swarm live, 300 Kimi K2.6 agents firing in parallel, then Opus 4.8 checking every single output against its source. this is not just a faster swarm. it is a loop that refuses to stop while anything is still wrong he pointed it at 100 EV-market companies. first pass: 12 failed. wrong revenue, dead citations, empty fields. second pass: 3 failed. third pass: zero this is not another agent demo. it is a system that catches its own mistakes before he reads a single row

A 21-YEAR-OLD FROM CHINA RUNS 300 AI AGENTS AT ONCE. THE PART THAT MATTERS ISN'T THE SPEED, IT'S THAT NONE OF THEM CAN LIE TO HIM he opens the dashboard and shows the swarm live, 300 Kimi K2.6 agents firing in parallel, then Opus 4.8 checking every single output against its source. this is not just a faster swarm. it is a loop that refuses to stop while anything is still wrong he pointed it at 100 EV-market companies. first pass: 12 failed. wrong revenue, dead citations, empty fields. second pass: 3 failed. third pass: zero this is not another agent demo. it is a system that catches its own mistakes before he reads a single row

NO1ennn

6,947,081 görüntüleme • 1 ay önce

ChatGPT can write you a thousand trading strategies from one sentence. 999 will quietly bleed your account dry. Every single one of them looks like a winner. One method pulls the real one out. Quant desks have run it for years. It's called loop engineering. It's not a smarter prompt. It's a loop: generate a strategy, test it, score why it failed, feed that back, and run it again until one survives data it has never seen. Man Group runs $150 billion. They built an AI that writes and tests hundreds of strategies a week. And second agent whose only job is to hunt the ones that secretly overfit and kill them before a cent goes live. > describe an idea -> backtest 5 years in 12 seconds > read why it died -> feed that back in > run it again until one survives data it never saw AI can write a thousand strategies. Loop engineering is the only thing that tells you which one was ever real. 89% of retail lost money in 2025. Almost none of it from bad ideas. All of it from trading the first guess and never running it through backtest loop. Horizon just put the whole thing in a chat box, free while the beta's open: You're not losing to smarter traders. You're losing to the ones who opened the tab. Anyone can generate a strategy now. Almost no one runs the loop that proves it. That gap is the whole edge. You'll mean to check it later. Later is a "waitlist closed" page.

ChatGPT can write you a thousand trading strategies from one sentence. 999 will quietly bleed your account dry. Every single one of them looks like a winner. One method pulls the real one out. Quant desks have run it for years. It's called loop engineering. It's not a smarter prompt. It's a loop: generate a strategy, test it, score why it failed, feed that back, and run it again until one survives data it has never seen. Man Group runs $150 billion. They built an AI that writes and tests hundreds of strategies a week. And second agent whose only job is to hunt the ones that secretly overfit and kill them before a cent goes live. > describe an idea -> backtest 5 years in 12 seconds > read why it died -> feed that back in > run it again until one survives data it never saw AI can write a thousand strategies. Loop engineering is the only thing that tells you which one was ever real. 89% of retail lost money in 2025. Almost none of it from bad ideas. All of it from trading the first guess and never running it through backtest loop. Horizon just put the whole thing in a chat box, free while the beta's open: You're not losing to smarter traders. You're losing to the ones who opened the tab. Anyone can generate a strategy now. Almost no one runs the loop that proves it. That gap is the whole edge. You'll mean to check it later. Later is a "waitlist closed" page.

cvxv666

173,703 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

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 • 29 gün önce

Automation engineer sent two AI to war. One fights to place the trade. The other fights to prove it's a mistake. Only what survives the battle gets his money - $392,000 profit of it so far. He doesn't pick the trades anymore. He built loop and stepped back. His wallet: The article below explains why that second AI, the one whose only job is to say no - is the entire game. Without a real check, you don't have a loop. You have a model agreeing with itself until the account's empty. He builds these loops for a living - agents that ship code and run themselves. One weekend he built one that trades. Here's how the war actually plays out. The maker reads the 5-minute candle and builds a case: buy Up, here's why. The checker has one purpose - break that case. Wrong regime, thin edge, bad timing. Poke one hole and the trade dies on the spot. Only the trades the checker can't kill ever reach the market. Every night the loop writes down which calls went wrong and tightens its own rules. It stops itself cold at the daily loss cap - nothing runs forever. $5,000 → $392,000. The checker vetoes far more trades than it lets through. That's the point. He didn't build a smarter bot. He built one that has to win an argument before it spends a dollar. Save this and read the breakdown below - it's the clearest explanation of loop engineering on your timeline, and it's the exact idea this whole system runs on. Or skip the build: the loop's live right now, two AI arguing over the next candle. Two clicks and its winners land in your wallet too:

Automation engineer sent two AI to war. One fights to place the trade. The other fights to prove it's a mistake. Only what survives the battle gets his money - $392,000 profit of it so far. He doesn't pick the trades anymore. He built loop and stepped back. His wallet: The article below explains why that second AI, the one whose only job is to say no - is the entire game. Without a real check, you don't have a loop. You have a model agreeing with itself until the account's empty. He builds these loops for a living - agents that ship code and run themselves. One weekend he built one that trades. Here's how the war actually plays out. The maker reads the 5-minute candle and builds a case: buy Up, here's why. The checker has one purpose - break that case. Wrong regime, thin edge, bad timing. Poke one hole and the trade dies on the spot. Only the trades the checker can't kill ever reach the market. Every night the loop writes down which calls went wrong and tightens its own rules. It stops itself cold at the daily loss cap - nothing runs forever. $5,000 → $392,000. The checker vetoes far more trades than it lets through. That's the point. He didn't build a smarter bot. He built one that has to win an argument before it spends a dollar. Save this and read the breakdown below - it's the clearest explanation of loop engineering on your timeline, and it's the exact idea this whole system runs on. Or skip the build: the loop's live right now, two AI arguing over the next candle. Two clicks and its winners land in your wallet too:

cvxv666

42,548 görüntüleme • 1 ay önce

A few weeks ago the US government forced Claude Fable 5 offline. It's back. And before they switch it off again, this is your shot to point the most powerful AI on earth at something of your own. Take the 26-year-old in Toronto. His bot went dark the day Fable 5 got pulled. The day it came back, it woke up and started printing again - $568,000 profit and counting. His wallet: Here's the story. When the ban hit, Anthropic had to switch Fable 5 off for everyone. They called it a misunderstanding with the government. Whatever it was, every bot running on that model stopped cold. His was one of them. He didn't rebuild a thing. The loop just sat there, paused, for weeks. Here's what that loop actually does. It's not one prompt to an AI. It's an agentic loop: a team of agents running on repeat. One reads the market, one places the trade, one tries to prove it wrong before a cent moves. Then it goes again, around the clock, keeping what works and dropping what doesn't. Fable 5 is the brain running that team. The exact model the government decided was too powerful to leave on. Point it at Bitcoin's 5-minute markets and it barely misses. Most of its trades close green, and it runs itself. He checks it from his phone. The government could switch off the model. It couldn't switch off the idea. Now the model's back, and so is the money. Save this before next headline. You'll want it the day Fable 5 hits offline again.

A few weeks ago the US government forced Claude Fable 5 offline. It's back. And before they switch it off again, this is your shot to point the most powerful AI on earth at something of your own. Take the 26-year-old in Toronto. His bot went dark the day Fable 5 got pulled. The day it came back, it woke up and started printing again - $568,000 profit and counting. His wallet: Here's the story. When the ban hit, Anthropic had to switch Fable 5 off for everyone. They called it a misunderstanding with the government. Whatever it was, every bot running on that model stopped cold. His was one of them. He didn't rebuild a thing. The loop just sat there, paused, for weeks. Here's what that loop actually does. It's not one prompt to an AI. It's an agentic loop: a team of agents running on repeat. One reads the market, one places the trade, one tries to prove it wrong before a cent moves. Then it goes again, around the clock, keeping what works and dropping what doesn't. Fable 5 is the brain running that team. The exact model the government decided was too powerful to leave on. Point it at Bitcoin's 5-minute markets and it barely misses. Most of its trades close green, and it runs itself. He checks it from his phone. The government could switch off the model. It couldn't switch off the idea. Now the model's back, and so is the money. Save this before next headline. You'll want it the day Fable 5 hits offline again.

cvxv666

24,055 görüntüleme • 1 ay önce

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.

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

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 > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

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 > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

Dep

20,895 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.

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

Jane Street spent $6 billion and 4,032 GPUs on one thing: AI agents that loop through trading strategies 100x faster than any human. Generate, backtest, kill, repeat - thousands a week, until one survives data it's never seen. That loop is why they made $39.6 billion last year while 89% of retail went broke trading one idea they never stress-tested. The edge was never a smarter idea. It was volume. They test 100 strategies for every 1 you test by hand, and a second agent kills the 97 that only look good on old data before a dollar goes live. Now the entire loop fits in a chat box. Horizon takes one plain-English sentence and spins up the same two agents. One builds your strategy, one tries to kill it - backtests 5 years in seconds, and only what survives goes live on your exchange. The $150 billion setup. Free while beta open. Bookmark this & read the full breakdown below - the exact two-agent loop, step by step, and who just handed it to retail.

Jane Street spent $6 billion and 4,032 GPUs on one thing: AI agents that loop through trading strategies 100x faster than any human. Generate, backtest, kill, repeat - thousands a week, until one survives data it's never seen. That loop is why they made $39.6 billion last year while 89% of retail went broke trading one idea they never stress-tested. The edge was never a smarter idea. It was volume. They test 100 strategies for every 1 you test by hand, and a second agent kills the 97 that only look good on old data before a dollar goes live. Now the entire loop fits in a chat box. Horizon takes one plain-English sentence and spins up the same two agents. One builds your strategy, one tries to kill it - backtests 5 years in seconds, and only what survives goes live on your exchange. The $150 billion setup. Free while beta open. Bookmark this & read the full breakdown below - the exact two-agent loop, step by step, and who just handed it to retail.

cvxv666

317,059 görüntüleme • 1 ay önce

the loop is not the whole agent it is only one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls iteration turns retries budgets stop conditions success checks stalled progress use durable execution when the run must survive crashes → GRAPH ENGINEERING controls structure nodes edges state branches checkpoints routing handoffs build stateful agents as explicit graphs → inspect the topology without putting a model in the loop → HARNESS ENGINEERING controls exposure tools permissions memory sandboxes evals traces humans isolate generated code from the host machine → test behavior before users ever see it → preserve one trace across every model step and tool call → without loop control it keeps running without graph structure the path stays invisible without harness control it can reach anything the loop runs inside the graph the graph runs inside the harness the model is only one component debug the layer that actually owns the failure save this then read the article below

the loop is not the whole agent it is only one layer of the system LOOP vs GRAPH vs HARNESS ENGINEERING LOOP ENGINEERING controls iteration turns retries budgets stop conditions success checks stalled progress use durable execution when the run must survive crashes → GRAPH ENGINEERING controls structure nodes edges state branches checkpoints routing handoffs build stateful agents as explicit graphs → inspect the topology without putting a model in the loop → HARNESS ENGINEERING controls exposure tools permissions memory sandboxes evals traces humans isolate generated code from the host machine → test behavior before users ever see it → preserve one trace across every model step and tool call → without loop control it keeps running without graph structure the path stays invisible without harness control it can reach anything the loop runs inside the graph the graph runs inside the harness the model is only one component debug the layer that actually owns the failure save this then read the article below

rari

20,934 görüntüleme • 7 gün önce

ANTHROPIC'S LEAD ENGINEER LEAKED A $1.2M SYSTEM THAT TURNS ONE ENGINEER INTO A FLEET OF 10 LOOPS your hands were the bottleneck all along - here are 8 steps that change that stop writing, start delegating - loop: feature, loop: bugfix, loop: tests - each runs independently and ships in parallel CLAUDE.md is law - every agent reads one file before acting - ten agents, one voice, zero chaos Opus 5 breaks the task into 3 independent subtasks - a bad plan multiplied by 10 workers equals 10 disasters each agent gets an isolated git worktree - three features land in the repo while you review one crash at hour 3 means resume at hour 3 not zero - without this you lose hours every day every loop writes its findings to the shared graph - worker 3 never repeats worker 1's dead end at night CLAUDE.md patches itself based on failures - tomorrow the fleet wakes up smarter save this and paste into Claude Code - and your first fleet of 10 loops is already running

ANTHROPIC'S LEAD ENGINEER LEAKED A $1.2M SYSTEM THAT TURNS ONE ENGINEER INTO A FLEET OF 10 LOOPS your hands were the bottleneck all along - here are 8 steps that change that stop writing, start delegating - loop: feature, loop: bugfix, loop: tests - each runs independently and ships in parallel CLAUDE.md is law - every agent reads one file before acting - ten agents, one voice, zero chaos Opus 5 breaks the task into 3 independent subtasks - a bad plan multiplied by 10 workers equals 10 disasters each agent gets an isolated git worktree - three features land in the repo while you review one crash at hour 3 means resume at hour 3 not zero - without this you lose hours every day every loop writes its findings to the shared graph - worker 3 never repeats worker 1's dead end at night CLAUDE.md patches itself based on failures - tomorrow the fleet wakes up smarter save this and paste into Claude Code - and your first fleet of 10 loops is already running

Sprytix

61,481 görüntüleme • 15 gün önce

I let a loop of AI agents build GTA 6 while I slept. Woke up to a dead Mac and a half walking NPC. Day 8. We're moving the whole game from Godot to Unreal, and the agents kept shipping right through it: - the first NPC walks but no animations - in-game phone now has maps, contacts, and a wallet. Bad news: the Mac died overnight because every agent opened the game at once to screenshot it. Fix was one line in claude.md, only one game or editor open at a time. Agents are back to looping, one at a time. Tomorrow: finish converting the entire repo to Unreal, and work the walk animation so the NPC actually looks real. The loop keeps building the phone apps, and I might pull the map onto the phone so the whole thing feels seamless. One catch: the licensed Unreal assets can't be shared publicly, so that part stays in a private build.

I let a loop of AI agents build GTA 6 while I slept. Woke up to a dead Mac and a half walking NPC. Day 8. We're moving the whole game from Godot to Unreal, and the agents kept shipping right through it: - the first NPC walks but no animations - in-game phone now has maps, contacts, and a wallet. Bad news: the Mac died overnight because every agent opened the game at once to screenshot it. Fix was one line in claude.md, only one game or editor open at a time. Agents are back to looping, one at a time. Tomorrow: finish converting the entire repo to Unreal, and work the walk animation so the NPC actually looks real. The loop keeps building the phone apps, and I might pull the map onto the phone so the whole thing feels seamless. One catch: the licensed Unreal assets can't be shared publicly, so that part stays in a private build.

Ziwen

290,991 görüntüleme • 1 ay önce

ChatGPT told your trading strategy was profitable. You went live. Two weeks later your account was bleeding out. That's not his fault. It handed you a guess and called it an edge. You're missing the one skill that separates quants from the retail they feed on: loop engineering. Horizon is the first tool that hands it to you - absolutely free: Here's the actual problem. ChatGPT can generate a thousand trading strategies in a minute. It cannot tell you which one actually works. 999 are noise. The one real edge is buried in there, and from the outside it looks exactly like the junk. So you trade the junk, lose, and call it a skill issue. Loop engineering does the opposite. It tests all thousand instead of trusting one - generate, score, kill, refine, repeat - and keeps only what survives data it never saw. That's the entire gap between you and a quant desk. Not brains. Not capital. The loop. It's why they print billions and 89% of retail funded them last year. Horizon runs that exact loop end to end: > a 5-year backtest in 12 seconds > thousands of simulated paths > out-of-sample gate before a dollar goes live The machine that cost a $25,000 terminal and a row of PhDs - now a sentence and a login. Save this - it's full framework below. Fewer than 1,300 seats left before launch locks the list. Link at the top - don't be the one who read all this and skip.

ChatGPT told your trading strategy was profitable. You went live. Two weeks later your account was bleeding out. That's not his fault. It handed you a guess and called it an edge. You're missing the one skill that separates quants from the retail they feed on: loop engineering. Horizon is the first tool that hands it to you - absolutely free: Here's the actual problem. ChatGPT can generate a thousand trading strategies in a minute. It cannot tell you which one actually works. 999 are noise. The one real edge is buried in there, and from the outside it looks exactly like the junk. So you trade the junk, lose, and call it a skill issue. Loop engineering does the opposite. It tests all thousand instead of trusting one - generate, score, kill, refine, repeat - and keeps only what survives data it never saw. That's the entire gap between you and a quant desk. Not brains. Not capital. The loop. It's why they print billions and 89% of retail funded them last year. Horizon runs that exact loop end to end: > a 5-year backtest in 12 seconds > thousands of simulated paths > out-of-sample gate before a dollar goes live The machine that cost a $25,000 terminal and a row of PhDs - now a sentence and a login. Save this - it's full framework below. Fewer than 1,300 seats left before launch locks the list. Link at the top - don't be the one who read all this and skip.

cvxv666

18,985 görüntüleme • 1 ay önce

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,186 görüntüleme • 2 ay önce

Introducing Loop The autonomous business manager that runs your outreach, your follow-ups, and your pipeline,while you focus on the work only you can do. Loop doesn't live in your inbox. Your inbox lives in Loop. Reads every lead like a teammate who's been on your team for years Writes the reply, makes the call, chases the deal when email goes cold Pauses the moment a human actually needs to show up Replaces the patchwork of CRMs, outreach tools, and follow-up apps with one system that does the work Stop managing tools. Start running your loop. comment "loop" and we'll send you in. loop

Introducing Loop The autonomous business manager that runs your outreach, your follow-ups, and your pipeline,while you focus on the work only you can do. Loop doesn't live in your inbox. Your inbox lives in Loop. Reads every lead like a teammate who's been on your team for years Writes the reply, makes the call, chases the deal when email goes cold Pauses the moment a human actually needs to show up Replaces the patchwork of CRMs, outreach tools, and follow-up apps with one system that does the work Stop managing tools. Start running your loop. comment "loop" and we'll send you in. loop

Anushka Singh

12,881 görüntüleme • 2 ay önce

Run your coding agent on a local model, with QVAC. OpenCode now plugs into a model on your own machine through our official plugin. That changes two things. Privacy by default. Your repo, your prompts, and every command the agent runs stay on your device. No third-party model ever sees your code. For an agent that reads your codebase and runs commands, that is the point, not a nice-to-have. New workflows. With no meter and no rate limit, the agent does not have to stop. Let it loop on a task, refactor a whole repo overnight, or run a watch-build-fix loop that keeps going. Setup takes a few minutes: one line in opencode.json and OpenCode runs on a local QVAC model. In the video demo, it handles three real developer tasks back to back, fully offline.

Run your coding agent on a local model, with QVAC. OpenCode now plugs into a model on your own machine through our official plugin. That changes two things. Privacy by default. Your repo, your prompts, and every command the agent runs stay on your device. No third-party model ever sees your code. For an agent that reads your codebase and runs commands, that is the point, not a nice-to-have. New workflows. With no meter and no rate limit, the agent does not have to stop. Let it loop on a task, refactor a whole repo overnight, or run a watch-build-fix loop that keeps going. Setup takes a few minutes: one line in opencode.json and OpenCode runs on a local QVAC model. In the video demo, it handles three real developer tasks back to back, fully offline.

QVAC

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

THIS GUY CONNECTED CLAUDE TO TRADINGVIEW AND CUT 200+ HOURS OF MANUAL CHART WORK 40 trades a week used to mean the same loop: open the chart, check RSI, compare EMA, write notes and wait for the next setup now Claude reads TradingView 24/7, tracks volume, indicators and price conditions while he is not even at the desk this is not a $20k trading terminal and not a quant fund setup, just one laptop, one chart and one strategy written in plain English the crazy part is not that Claude predicts the market, it is that a regular trader can remove the boring human loop from every setup ↓

THIS GUY CONNECTED CLAUDE TO TRADINGVIEW AND CUT 200+ HOURS OF MANUAL CHART WORK 40 trades a week used to mean the same loop: open the chart, check RSI, compare EMA, write notes and wait for the next setup now Claude reads TradingView 24/7, tracks volume, indicators and price conditions while he is not even at the desk this is not a $20k trading terminal and not a quant fund setup, just one laptop, one chart and one strategy written in plain English the crazy part is not that Claude predicts the market, it is that a regular trader can remove the boring human loop from every setup ↓

Gipp 🦅

55,610 görüntüleme • 2 ay önce

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

Sprytix

37,766 görüntüleme • 13 gün önce