Загрузка видео...

Не удалось загрузить видео

На главную

US export-control disable Claude Fable 5 overnight. Not for what it said - for what one trader did with it. He turned an $11,000 wreck into $300,000 profit in five days. Then they pulled Claude Fable 5 from public hands. Too late - his bot's still running. His wallet:...

77,026 просмотров • 26 дней назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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,743 просмотров • 29 дней назад

I built my own charting platform with Claude Fable, and it does a few things Tradingview straight up can't.. I call it EchoCharts.. so what it basically does is 1) Echoes: this is the big one. it takes the exact shape price action is forming right now them scans thousands of past candles, and finds every time the market looked just like this before. then it shows you what happened next. it'll tell you something like "20 matches, 30% closed higher 24 bars later, median -0.05%", and it draws those past paths forward on the chart so you see the full spread. 2) Sketch search: draw any shape with your mouse, and it finds where price actually did that in real history, then jumps you straight to it. great for the patterns you can feel but can't name. 3) Market clock: A 24-hour dial showing when this market actually moves. volatility, direction and volume, split by hour of the day and day of the week. so you stop trading dead hours and start trading when it counts. plus the basics done clean, candles, volume, a moving average, and RSI. So how it basically works is, it all runs on real binance data, 6,000 live candles.. Echoes matches the shape of the move using correlation, not the price level, so a setup today of bitcoin:native at $63K can match one from years ago at $10K and it only ever looks at fully finished history, it never peeks at the future, so the "what happened next" numbers stay honest. Now, Here’s how i built it: i described what i wanted and claude fable built it. plain javascript, the lightweight-charts library for the chart, around 700 lines, no framework. static site, opens in any browser. one thing i'll be straight about, echoes shows you what happened after similar setups in the past. that's history, not a prediction. it shows you the lay of the land, it doesn't call the future. might open-source the whole thing soon.

Axel Bitblaze 🪓

54,755 просмотров • 27 дней назад

Japan just changed what an AI model even is. New Sakana Fugu doesn't try to out-think GPT-5, Claude, or Gemini. It conducts all three at once - and beats every one of them. A trader in Tokyo unleashed it on the fastest market alive - 5min Bitcoin binary and turned $6,200 into $304,865. His wallet: The frontier just stopped being which model is smartest. It's who's conducting them - and the market hasn't priced that in yet. Sakana Fugu isn't a bigger model - it's a full multi-agent orchestration system. The coordinator behind it carries about 10,000 parameters, evolved rather than hand-coded, and it runs the most capable models on earth like a single instrument. Pointed at Bitcoin, here's what it does every five minutes. It assembles a team from a pool of frontier models and assigns each one a role: > Thinker - reads the candle, the order book, the news, builds the plan > Worker - turns the plan into one call: up or down, and how much > Verifier - votes ACCEPT or REVISE before a cent moves If the Verifier says REVISE, nothing trades. Fugu reads its own miss, reroutes, even calls itself for a corrective round, and runs it again. No look-ahead, ever - the next candle only appears after it commits. This is what should worry every lab still chasing a bigger model: the edge was never scale. It's orchestration - and Fugu does it better than anything alive. Bookmark this - when the whole timeline is chasing orchestration in six months, you'll already have the breakdown. You're not going to wire up an orchestra of frontier models yourself. Mirror the wallet Fugu runs instead:

cvxv666

72,821 просмотров • 16 дней назад