Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

> Opus 4.8 shipped a dial most people won't touch > type /effort in claude code > a menu of compute levels opens up > low for quick stuff, max for the hardest > the one to know: ultracode > xhigh thinking + automatic workflow orchestration > point it...

RetroChainer's profile picture

RetroChainer

6,111 subscribers

18,244 görüntüleme • 4 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

26 Yorum

RetroChainer profil fotoğrafı
RetroChainer4 ay önce

More in my private Telegram: AI tools and workflows, prediction-market breakdowns with the structure, and the mechanics of X growth. It all lands there before the feed.

Paulo Nick profil fotoğrafı
Paulo Nick4 ay önce

Amazing

kiruwaaaa profil fotoğrafı
kiruwaaaa4 ay önce

Now we are waiting for myths

T_Khanh2026.eth profil fotoğrafı
T_Khanh2026.eth4 ay önce

keen to try ultracode on real work

Kai🔺 profil fotoğrafı
Kai🔺4 ay önce

this dial thing sounds like the real game changer

beamnxw ./ profil fotoğrafı
beamnxw ./4 ay önce

ultracode mode is going to incinerate token limits fast

JMoon profil fotoğrafı
JMoon4 ay önce

ultracode on a half-baked spec is how you get 800 lines of perfectly structured wrong. the dial matters less than the brief.

Harry Tandy profil fotoğrafı
Harry Tandy4 ay önce

finally we can trade time for pure execution quality

Nick Venturi profil fotoğrafı
Nick Venturi4 ay önce

putting it on ultracode just to find where i missed a semicolon

アキラ profil fotoğrafı
アキラ4 ay önce

Opus 4.8 với ultracode, xhigh, hãy thử!

yomi profil fotoğrafı
yomi4 ay önce

我的任务，我如何知道需要使用的深度是什么等级？

安叫兽|Bird🕊️ 🔶 BNB profil fotoğrafı
安叫兽|Bird🕊️ 🔶 BNB4 ay önce

这个旋钮怕是一开就停不下来

Ivdr profil fotoğrafı
Ivdr4 ay önce

In your opinion, is Cloud currently the top LLM model?

Alpha Batcher profil fotoğrafı
Alpha Batcher4 ay önce

just be Opus 4.8 user and life will good bro

sandybrige profil fotoğrafı
sandybrige4 ay önce

興味深い機能がありますね!

Levi profil fotoğrafı
Levi4 ay önce

so basically we’re adjusting tge brain’s wattage mid conversation now huh

JennyLiu profil fotoğrafı
JennyLiu4 ay önce

feels like the first time we can actually tune cognition instead of size wild that it’s same rate across the dial

Anatole Clement profil fotoğrafı
Anatole Clement4 ay önce

this is lowkey the secret sauce for power users

Long 7 profil fotoğrafı
Long 74 ay önce

この機能は本当にユーザーにとって便利で便利ですね。どれだけ深く探求したいかを選択できることが素晴らしいです。

Arthur frank profil fotoğrafı
Arthur frank4 ay önce

Absolutely amazing

Fokki profil fotoğrafı
Fokki4 ay önce

Another cool update from Claude

𝗢𝗠𝗘𝗚𝗔 profil fotoğrafı
𝗢𝗠𝗘𝗚𝗔4 ay önce

ultracode is the bet that planning beats inference orchestration scales what a single pass cannot

sandybrige profil fotoğrafı
sandybrige4 ay önce

この機能は本当に革新的ですね！計画から実行まで、全てがスムーズになりそうです。

Compile And Push profil fotoğrafı
Compile And Push4 ay önce

quiet work wins.

NMhao profil fotoğrafı
NMhao4 ay önce

エフォートがあるの？興味津々！効率向上のためには、自動化プロセスが重要だね。ありがと！

Saberin Samarat profil fotoğrafı
Saberin Samarat4 ay önce

Follow me please

Benzer Videolar

Anthropic just dropped Claude Opus 4.8 and it's too smart for its own good. Wes Roth spent 17 minutes breaking down exactly what changed and why it matters. New effort levels, low, medium, high, xhigh, max, ultracode, the harder the task the smarter it gets. No paywall, no course, just 17 minutes that change how you use Claude forever.
17:00

Anthropic just dropped Claude Opus 4.8 and it's too smart for its own good. Wes Roth spent 17 minutes breaking down exactly what changed and why it matters. New effort levels, low, medium, high, xhigh, max, ultracode, the harder the task the smarter it gets. No paywall, no course, just 17 minutes that change how you use Claude forever.

Defileo🔮

25,866 görüntüleme • 4 ay önce

> you pay $5,000 a year for AI > and still ration every request > AMD just broke that math > Ryzen AI Max+ 395. 200B on one die. > EVO-X2. Claude Code. one evening. > one variable and Claude Code points at your room > nothing leaves the network. nothing on the meter. > stop paying per token stop rationing > the edge isn't the cloud. it's the meter being off.
0:31

> you pay $5,000 a year for AI > and still ration every request > AMD just broke that math > Ryzen AI Max+ 395. 200B on one die. > EVO-X2. Claude Code. one evening. > one variable and Claude Code points at your room > nothing leaves the network. nothing on the meter. > stop paying per token stop rationing > the edge isn't the cloud. it's the meter being off.

RetroChainer

81,891 görüntüleme • 3 ay önce

this is the most insane thing i've seen an AI do all year an early tester gave Opus 5.5 one job: migrate 680,000 lines of code. a team would burn weeks on it it finished in under a day another let it run overnight across six repos, unattended. it stayed on task for over 18 hours a third pointed it at a 200,000-line codebase to audit and fix. Opus 5 took over 20 hours and 2.5x the tokens. Opus 5.5 did it in under three and it shipped today 40% cheaper than Opus 5 the part nobody's saying out loud: the bottleneck stopped being the model. it's now the size of the job you're brave enough to hand it so hand it a big one tonight, $0 on top of your sub: → point Claude at your messiest repo, the one you've been scared to touch → one sentence: "audit this end to end, fix what's broken, leave the risky calls for me to approve" → close the laptop. it runs while you sleep → morning: a diff, a list of what it fixed, and the judgment calls waiting for you six months from now the people who started tonight will have shipped the backlog they'd written off everyone else will still be "planning the refactor" bookmark this before your competitor runs it first
0:30

this is the most insane thing i've seen an AI do all year an early tester gave Opus 5.5 one job: migrate 680,000 lines of code. a team would burn weeks on it it finished in under a day another let it run overnight across six repos, unattended. it stayed on task for over 18 hours a third pointed it at a 200,000-line codebase to audit and fix. Opus 5 took over 20 hours and 2.5x the tokens. Opus 5.5 did it in under three and it shipped today 40% cheaper than Opus 5 the part nobody's saying out loud: the bottleneck stopped being the model. it's now the size of the job you're brave enough to hand it so hand it a big one tonight, $0 on top of your sub: → point Claude at your messiest repo, the one you've been scared to touch → one sentence: "audit this end to end, fix what's broken, leave the risky calls for me to approve" → close the laptop. it runs while you sleep → morning: a diff, a list of what it fixed, and the judgment calls waiting for you six months from now the people who started tonight will have shipped the backlog they'd written off everyone else will still be "planning the refactor" bookmark this before your competitor runs it first

Argona

28,850 görüntüleme • 12 gün önce

OPUS 4.6 WAS NERFED DUE TO DEMAND BUT OPUS 4.5 DOES NOT SEEM TO BE HIT this guy ran the same test on both models. Opus 4.6 fails consistently but Opus 4.5 passes every time he switched back to Opus 4.5 on Claude Code and said "what a difference, feels like i got Opus back finally" he is now using this test as a "quantization canary" that runs it at the start of every session before doing real work. if it fails, the model is degraded. five Opus 4.6 windows in a row failed the untransparent nerfing is pushing people to cancel their Max plans if you've been feeling like Opus got dumber lately, you're not imagining it i'd suggest switching to Opus 4.5 to see the difference for yourself
1:03

OPUS 4.6 WAS NERFED DUE TO DEMAND BUT OPUS 4.5 DOES NOT SEEM TO BE HIT this guy ran the same test on both models. Opus 4.6 fails consistently but Opus 4.5 passes every time he switched back to Opus 4.5 on Claude Code and said "what a difference, feels like i got Opus back finally" he is now using this test as a "quantization canary" that runs it at the start of every session before doing real work. if it fails, the model is degraded. five Opus 4.6 windows in a row failed the untransparent nerfing is pushing people to cancel their Max plans if you've been feeling like Opus got dumber lately, you're not imagining it i'd suggest switching to Opus 4.5 to see the difference for yourself

Om Patel

696,175 görüntüleme • 5 ay önce

AMD JUST KILLED THE $200 - A - MONTH AI SUBSCRIPTION - A 65-WATT BOX WITH 128GB OF UNIFIED MEMORY THAT RUNS 70B MODELS LOCALLY. that clip is amd's ryzen ai max+ 395 mini box, held up on stage. the whole pitch is one spec: 128gb of high-speed unified memory. why it matters: cpu, gpu and npu share the same 128gb pool, so a model that used to need a rack of vram just fits. what it actually runs: llama 70b in full precision on the built-in gpu open models up to ~100b parameters, locally, no cloud all of it in a mini pc pulling around 65 watts that's the part that ends the subscription: your prompts, your data, your model, on a box on your desk, not metered by the token. honest line: this runs open models, not gpt-5 or claude opus. for chat, coding help and agents on your own data it's more than enough. for the absolute frontier, the cloud still wins. and it isn't free: the box runs ~$1,500 and up. but that's a few months of a $200 sub, then it's yours forever. no monthly ai bill, no tokens metered, no prompt leaving the room. the uncomfortable part isn't that amd made a fast box. it's that "you need the cloud for ai" was a pricing choice, and unified memory just made it optional. follow RetroChainer for the hardware that turns rent into ownership, and bookmark this before your next ai renewal.
0:41

AMD JUST KILLED THE $200 - A - MONTH AI SUBSCRIPTION - A 65-WATT BOX WITH 128GB OF UNIFIED MEMORY THAT RUNS 70B MODELS LOCALLY. that clip is amd's ryzen ai max+ 395 mini box, held up on stage. the whole pitch is one spec: 128gb of high-speed unified memory. why it matters: cpu, gpu and npu share the same 128gb pool, so a model that used to need a rack of vram just fits. what it actually runs: llama 70b in full precision on the built-in gpu open models up to ~100b parameters, locally, no cloud all of it in a mini pc pulling around 65 watts that's the part that ends the subscription: your prompts, your data, your model, on a box on your desk, not metered by the token. honest line: this runs open models, not gpt-5 or claude opus. for chat, coding help and agents on your own data it's more than enough. for the absolute frontier, the cloud still wins. and it isn't free: the box runs ~$1,500 and up. but that's a few months of a $200 sub, then it's yours forever. no monthly ai bill, no tokens metered, no prompt leaving the room. the uncomfortable part isn't that amd made a fast box. it's that "you need the cloud for ai" was a pricing choice, and unified memory just made it optional. follow RetroChainer for the hardware that turns rent into ownership, and bookmark this before your next ai renewal.

RetroChainer

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

Introducing Claude Opus 5.5, the first model in our new Claude 5.5 family. It performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.
0:20

Introducing Claude Opus 5.5, the first model in our new Claude 5.5 family. It performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.

Claude

28,008,296 görüntüleme • 12 gün önce

Anthropic engineer: "You're not supposed to watch Claude Code work. You're supposed to wake up and review what it shipped." In 22 minutes she builds the whole workflow live, step by step. Most people close their laptop and everything stops, this setup keeps running in a loop and gets better the longer it works. Watch the video, then save the exact setup below.
21:31

Anthropic engineer: "You're not supposed to watch Claude Code work. You're supposed to wake up and review what it shipped." In 22 minutes she builds the whole workflow live, step by step. Most people close their laptop and everything stops, this setup keeps running in a loop and gets better the longer it works. Watch the video, then save the exact setup below.

Anatoli Kopadze

132,136 görüntüleme • 2 ay önce

Meg Stalter is carrying a bag with the word "Ceasefire" on it to the #Emmys. "It's the most important to stick up for people and for peace... We have to use our platforms. What's the point of being at these big events if you're not going to use your privilege?"
1:15

Meg Stalter is carrying a bag with the word "Ceasefire" on it to the #Emmys. "It's the most important to stick up for people and for peace... We have to use our platforms. What's the point of being at these big events if you're not going to use your privilege?"

Variety

185,994 görüntüleme • 1 yıl önce

FREE $100 for Claude Opus 5 on signup. Refer a friend and it jumps to $120. It's called Tabitoken (TabiAI). API access, $100 balance on signup, no card required. Inside: → claude-opus-5 and claude-opus-5-thinking → claude-opus-4-8 and claude-opus-4-8-thinking → Priced by token, not by request - Opus 4.8 runs $1/1M in, $5/1M out, Opus 5 runs $3/1M both ways → OpenAI, Claude, and Gemini API format compatibility - drop the key into any client with a custom endpoint Real math: at $3/1M for Opus 5, $100 covers roughly 33M tokens combined. Even moderate daily use stretches this for weeks before you touch a card. Setup: → Go to tabitoken(.)com → Sign up, claim your $100 → Grab your API key → Point any compatible client at it Bookmark this before they cut the starting balance.
0:58

FREE $100 for Claude Opus 5 on signup. Refer a friend and it jumps to $120. It's called Tabitoken (TabiAI). API access, $100 balance on signup, no card required. Inside: → claude-opus-5 and claude-opus-5-thinking → claude-opus-4-8 and claude-opus-4-8-thinking → Priced by token, not by request - Opus 4.8 runs $1/1M in, $5/1M out, Opus 5 runs $3/1M both ways → OpenAI, Claude, and Gemini API format compatibility - drop the key into any client with a custom endpoint Real math: at $3/1M for Opus 5, $100 covers roughly 33M tokens combined. Even moderate daily use stretches this for weeks before you touch a card. Setup: → Go to tabitoken(.)com → Sign up, claim your $100 → Grab your API key → Point any compatible client at it Bookmark this before they cut the starting balance.

Atenov int.

50,875 görüntüleme • 1 ay önce

Someone figured out how to run Claude Fable 5 and GPT-5.6 together inside ChatGPT Codex and the setup takes 5 minutes. Two commands get you started: → codex plugin marketplace add Cjbuilds/Codex-Orchestration → codex plugin add codex-orchestration@codex-orchestration From there you set an advisor model for the expensive thinking and an executor model for the cheaper implementation. Paste the workflow prompt, describe the task and both models handle their side automatically. Fable 5 plans. A cheaper model executes. You get the best of both without paying flagship prices for every token.
0:56

Someone figured out how to run Claude Fable 5 and GPT-5.6 together inside ChatGPT Codex and the setup takes 5 minutes. Two commands get you started: → codex plugin marketplace add Cjbuilds/Codex-Orchestration → codex plugin add codex-orchestration@codex-orchestration From there you set an advisor model for the expensive thinking and an executor model for the cheaper implementation. Paste the workflow prompt, describe the task and both models handle their side automatically. Fable 5 plans. A cheaper model executes. You get the best of both without paying flagship prices for every token.

0xMarioNawfal

56,586 görüntüleme • 2 ay önce

CLAUDE CODE JUST SHIPPED THE FEATURE THAT SOLVES THE BIGGEST PROBLEM EVERY BUILDER HAS WITH AI AGENTS. The problem: Claude starts a task, gets distracted by a sub-problem, goes down a rabbit hole, and never finishes the original thing you asked for. The solution: /goal One command. You set the goal at the start of the session. Claude now has a north star it checks against every action it takes. Not just at the beginning. Throughout the entire session. Every time Claude is about to do something it asks: does this action move me toward the goal the user set or am I drifting? If it is drifting it corrects. If it completes a sub-task it returns to the primary goal. If it hits a blocker it reports back instead of spending 45 minutes solving the wrong problem. This sounds like a small feature. It is not. The reason most people do not trust Claude Code for long autonomous runs is not capability. It is reliability. A Claude Code session that reliably finishes what it started is worth 10 times more than one that is more capable but wanders. /goal is the feature that makes long autonomous sessions reliable. Set the goal. Let it run. Come back to a finished result. Not a result that got 70% done before Claude decided the sub-problem was more interesting. Done. The builders running overnight agent sessions are going to use this command on everything from today forward. Bookmark this. Follow CyrilXBT for every Claude Code feature the moment it ships.
0:24

CLAUDE CODE JUST SHIPPED THE FEATURE THAT SOLVES THE BIGGEST PROBLEM EVERY BUILDER HAS WITH AI AGENTS. The problem: Claude starts a task, gets distracted by a sub-problem, goes down a rabbit hole, and never finishes the original thing you asked for. The solution: /goal One command. You set the goal at the start of the session. Claude now has a north star it checks against every action it takes. Not just at the beginning. Throughout the entire session. Every time Claude is about to do something it asks: does this action move me toward the goal the user set or am I drifting? If it is drifting it corrects. If it completes a sub-task it returns to the primary goal. If it hits a blocker it reports back instead of spending 45 minutes solving the wrong problem. This sounds like a small feature. It is not. The reason most people do not trust Claude Code for long autonomous runs is not capability. It is reliability. A Claude Code session that reliably finishes what it started is worth 10 times more than one that is more capable but wanders. /goal is the feature that makes long autonomous sessions reliable. Set the goal. Let it run. Come back to a finished result. Not a result that got 70% done before Claude decided the sub-problem was more interesting. Done. The builders running overnight agent sessions are going to use this command on everything from today forward. Bookmark this. Follow CyrilXBT for every Claude Code feature the moment it ships.

CyrilXBT

19,586 görüntüleme • 4 ay önce

EVERYONE'S BUYING THE M4 MAC MINI AS A CHEAP DESKTOP. HERE'S WHY IT ENDS UP UNUSED. the pitch is irresistible: a tiny mac that runs cool, quiet, and cheap. then the receipt shows up. the mac mini ships with no screen, no keyboard, no mouse. add a monitor, a decent keyboard and mouse, and more storage, and the "$799 mac" is past $1,000 fast. and macos isn't windows. if your world is gaming, specific windows apps, or the setup you already know, the mini fights you the whole way. that's how so many end up back on a pc, the mini in a drawer. so what is the mac mini actually great at? not being your main desktop. it's the box you never look at. headless in a corner, it's a near-silent always-on server: run local ai models on it, host your automations, keep your files, and reach it from the laptop you already use. it earns its keep by disappearing. the honest turn: the mac mini isn't a cheap desktop. it's a cheap server pretending to be one. buy it for the job it's quietly brilliant at, not the one the ads imply. want a main computer? price the whole setup first. want a silent little box that runs ai and never bothers you? this is the one. no monitor in the box, no keyboard, no "just $599". save this before you buy the sticker price instead of the real one.
0:34

EVERYONE'S BUYING THE M4 MAC MINI AS A CHEAP DESKTOP. HERE'S WHY IT ENDS UP UNUSED. the pitch is irresistible: a tiny mac that runs cool, quiet, and cheap. then the receipt shows up. the mac mini ships with no screen, no keyboard, no mouse. add a monitor, a decent keyboard and mouse, and more storage, and the "$799 mac" is past $1,000 fast. and macos isn't windows. if your world is gaming, specific windows apps, or the setup you already know, the mini fights you the whole way. that's how so many end up back on a pc, the mini in a drawer. so what is the mac mini actually great at? not being your main desktop. it's the box you never look at. headless in a corner, it's a near-silent always-on server: run local ai models on it, host your automations, keep your files, and reach it from the laptop you already use. it earns its keep by disappearing. the honest turn: the mac mini isn't a cheap desktop. it's a cheap server pretending to be one. buy it for the job it's quietly brilliant at, not the one the ads imply. want a main computer? price the whole setup first. want a silent little box that runs ai and never bothers you? this is the one. no monitor in the box, no keyboard, no "just $599". save this before you buy the sticker price instead of the real one.

RetroChainer

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

Anthropic engineer: "You're not supposed to watch Claude Code work. You're supposed to wake up and review what it shipped" in 22 minutes she builds the full workflow from scratch, step by step a routine that ships work while you sleep most developers have never seen Claude Code run without them watching watch the session, then save the guide below
21:33

Anthropic engineer: "You're not supposed to watch Claude Code work. You're supposed to wake up and review what it shipped" in 22 minutes she builds the full workflow from scratch, step by step a routine that ships work while you sleep most developers have never seen Claude Code run without them watching watch the session, then save the guide below

Anatoli Kopadze

36,289 görüntüleme • 4 ay önce

Stop what you're doing. Claude Opus 4.6 just released and it's incredible Both OpenClaw and Claude Code are 10x better with it It's now my daily driver for both In this video I cover EVERYTHING you need to know about Opus, and how to get the most out of it:
17:28

Stop what you're doing. Claude Opus 4.6 just released and it's incredible Both OpenClaw and Claude Code are 10x better with it It's now my daily driver for both In this video I cover EVERYTHING you need to know about Opus, and how to get the most out of it:

Alex Finn

72,614 görüntüleme • 8 ay önce

Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.
1:35

Everyone's sleeping on MiniMax. Again. They just shipped M3. The first open-weights model to combine frontier coding, 1M context, and native multimodality in one drop. I plugged it into Claude Code this morning. Pasted a design from Dribbble. Watched M3 write production-ready React code in one session. At the agency, I just replaced Opus 4.8 with M3 for 80% of our coding tasks. The output is the same and we are running everything at a fraction of the cost. Open infrastructure is the future.

Prajwal Tomar

12,904 görüntüleme • 4 ay önce

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,793 görüntüleme • 6 ay önce

We shipped a major upgrade to the Auto Router: It now routes based on what the market actually uses for each type of task. When the market migrates a workload to a new model, the router follows within days. Benchmarks & more 👇
1:47

We shipped a major upgrade to the Auto Router: It now routes based on what the market actually uses for each type of task. When the market migrates a workload to a new model, the router follows within days. Benchmarks & more 👇

OpenRouter

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

Pokee Isaac now runs inside Claude Code. And you can use it a few different ways: have Claude call Isaac for complete one-shot generations, switch directly to Isaac as your model mid-session, or run the entire Claude Code session on Isaac. For the workflow shown below, Claude plans and verifies. Isaac generates the complete artifact in a single pass. Integration built and open-sourced by ⭕ AI & Design (Marco). Here's a quick how-to video in order to get started! You can access the repo at:
2:03

Pokee Isaac now runs inside Claude Code. And you can use it a few different ways: have Claude call Isaac for complete one-shot generations, switch directly to Isaac as your model mid-session, or run the entire Claude Code session on Isaac. For the workflow shown below, Claude plans and verifies. Isaac generates the complete artifact in a single pass. Integration built and open-sourced by ⭕ AI & Design (Marco). Here's a quick how-to video in order to get started! You can access the repo at:

Pokee AI

41,078 görüntüleme • 1 ay önce

ANTHROPIC'S PRODUCT CHIEF HAS USED CLAUDE FABLE 5 FOR MONTHS BEFORE ANYONE ELSE. HERE'S WHAT HE LEARNED ABOUT THE MOST POWERFUL MODEL YET Mike Krieger co-founded Instagram and now runs product at Anthropic. He's had Claude Fable 5 for two months before the public, and his takeaway is that it changes how you have to work, not just how much you get done. Here's what stood out, and what to actually do with it 1. It holds the whole project, so stop chopping tasks small. The old habit was breaking work into model-sized pieces and stitching them. Fable keeps the whole thing in context. What to do: stop pre-slicing your prompts into tiny steps. Hand it the full goal and the intent behind it, the way you'd brief a senior engineer, and let it sequence the work itself 2. Delegate big, async, and overnight. He sets it on a hard task at night and wakes to it finished, including the model getting itself unstuck when a service died, scaffolding a workaround, and documenting it. What to do: stop babysitting one prompt at a time. Kick off long jobs and walk away. Run several sessions at once instead of one you watch 3. The skill is planning now, not typing. His day moved to long architecture conversations up front, then execution in chunks. What to do: spend your first prompts planning, not building. Then ask it to output an HTML page or markdown doc of the plan so your team aligns before any code is written. That early alignment is the new leverage 4. Match the effort level to the task. Fable's range is wide, so a heavy reasoning pass on a tiny UI tweak is overkill (and pricey). What to do: dial effort down for small jobs, save the deep thinking for hard ones. And don't use your most expensive model for quick questions, keep a fast model for those 5. Verification is the real bottleneck now. The hard part isn't getting output, it's trusting it. What to do: make every change ship with proof. Have Claude attach a screenshot or video of what it built, so you can see the result instead of reading the diff. Then stand behind the decisions yourself before you merge 6. Cost is per-result, not per-turn. Fable is expensive per call but often one-shots what other models need ten turns to get right. What to do: judge cost by what it takes to finish the task to your satisfaction, not the price of a single message. Give it a real task and see how far it gets before you jump in His bigger point: software engineering isn't over, it's different. The craft moved from writing code to owning intent, taste, and what actually ships. The floor rose so anyone can build, and the ceiling rose so experts go further than before Bookmark this
52:06

ANTHROPIC'S PRODUCT CHIEF HAS USED CLAUDE FABLE 5 FOR MONTHS BEFORE ANYONE ELSE. HERE'S WHAT HE LEARNED ABOUT THE MOST POWERFUL MODEL YET Mike Krieger co-founded Instagram and now runs product at Anthropic. He's had Claude Fable 5 for two months before the public, and his takeaway is that it changes how you have to work, not just how much you get done. Here's what stood out, and what to actually do with it 1. It holds the whole project, so stop chopping tasks small. The old habit was breaking work into model-sized pieces and stitching them. Fable keeps the whole thing in context. What to do: stop pre-slicing your prompts into tiny steps. Hand it the full goal and the intent behind it, the way you'd brief a senior engineer, and let it sequence the work itself 2. Delegate big, async, and overnight. He sets it on a hard task at night and wakes to it finished, including the model getting itself unstuck when a service died, scaffolding a workaround, and documenting it. What to do: stop babysitting one prompt at a time. Kick off long jobs and walk away. Run several sessions at once instead of one you watch 3. The skill is planning now, not typing. His day moved to long architecture conversations up front, then execution in chunks. What to do: spend your first prompts planning, not building. Then ask it to output an HTML page or markdown doc of the plan so your team aligns before any code is written. That early alignment is the new leverage 4. Match the effort level to the task. Fable's range is wide, so a heavy reasoning pass on a tiny UI tweak is overkill (and pricey). What to do: dial effort down for small jobs, save the deep thinking for hard ones. And don't use your most expensive model for quick questions, keep a fast model for those 5. Verification is the real bottleneck now. The hard part isn't getting output, it's trusting it. What to do: make every change ship with proof. Have Claude attach a screenshot or video of what it built, so you can see the result instead of reading the diff. Then stand behind the decisions yourself before you merge 6. Cost is per-result, not per-turn. Fable is expensive per call but often one-shots what other models need ten turns to get right. What to do: judge cost by what it takes to finish the task to your satisfaction, not the price of a single message. Give it a real task and see how far it gets before you jump in His bigger point: software engineering isn't over, it's different. The craft moved from writing code to owning intent, taste, and what actually ships. The floor rose so anyone can build, and the ceiling rose so experts go further than before Bookmark this

Yarchi

30,958 görüntüleme • 3 ay önce