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

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

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Sonnet as the main model, Opus as an advisor, and Haiku for subagents Save this and try it with one of your sessions Install: npx claude-code-templates@latest --setting model/sonnet-opus-advisor-haiku-subagents This command installs the settings required to configure your Claude Code sessions with this model distribution Select the appropriate configuration scope:... show more

Daniel San

34,832 subscribers

28,256 просмотров • 4 дней назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

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

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

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

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

Claude Coders: Pair Haiku 5.5 with an Opus advisor *NOW*. Opus 5.5 checks Haiku's work. Take advantage of the speed and cost-efficiency of Haiku with the intelligence of Opus. Copy this into settings.json (or ask Claude to): {"model":"haiku","advisorModel":"opus"}

Claude Coders: Pair Haiku 5.5 with an Opus advisor NOW. Opus 5.5 checks Haiku's work. Take advantage of the speed and cost-efficiency of Haiku with the intelligence of Opus. Copy this into settings.json (or ask Claude to): {"model":"haiku","advisorModel":"opus"}

Dan McAteer

113,517 просмотров • 5 дней назад

Absolutely recommend using Cache Control in Claude Code Probably one of the Mods that will save you the most tokens and help keep your sessions going much longer It adds this bar for Claude’s 5 minute cache and sends notifications to help keep the cache warm Install command: npx claude-code-templates@latest --mod observability/prompt-cache-control

Absolutely recommend using Cache Control in Claude Code Probably one of the Mods that will save you the most tokens and help keep your sessions going much longer It adds this bar for Claude’s 5 minute cache and sends notifications to help keep the cache warm Install command: npx claude-code-templates@latest --mod observability/prompt-cache-control

Daniel San

229,508 просмотров • 10 дней назад

To make it easier to migrate your workflows, we've updated the claude-api skill in Claude Code with Opus 4.7 support. Just say "migrate to Opus 4.7" and it updates model names, prompts, and effort settings for you.

To make it easier to migrate your workflows, we've updated the claude-api skill in Claude Code with Opus 4.7 support. Just say "migrate to Opus 4.7" and it updates model names, prompts, and effort settings for you.

ClaudeDevs

362,588 просмотров • 6 месяцев назад

Sonnet 5 is here. It's worse than Opus 4.8 on nearly every benchmark... Does that mean it's useless? Absolutely not. Use it with Claude Code Dynamic Workflows! 1. /model set to Sonnet 5 2. /effort set to Ultracode 3. Any complex task will kick off a dynamic workflow This will only become more powerful when Fable is back. You'll use Fable 5 as the superintelligent advisor and Sonnet 5 as the fast and efficient implementer.

Sonnet 5 is here. It's worse than Opus 4.8 on nearly every benchmark... Does that mean it's useless? Absolutely not. Use it with Claude Code Dynamic Workflows! 1. /model set to Sonnet 5 2. /effort set to Ultracode 3. Any complex task will kick off a dynamic workflow This will only become more powerful when Fable is back. You'll use Fable 5 as the superintelligent advisor and Sonnet 5 as the fast and efficient implementer.

Dan McAteer

666,124 просмотров • 3 месяцев назад

Claude Code has a new wild feature... dynamic workflow. How to try: set /model to opus 4.8 set /effort to "ultracode" 😂 use “workflow” in your prompt Claude will write an orchestration script, spawn subagents swarm, verify results, and report back.

Claude Code has a new wild feature... dynamic workflow. How to try: set /model to opus 4.8 set /effort to "ultracode" 😂 use “workflow” in your prompt Claude will write an orchestration script, spawn subagents swarm, verify results, and report back.

Min Choi

353,001 просмотров • 4 месяцев назад

This is f*cking insane. This tip saved me thousands of dollars. run Opus 5.5, Sonnet 5.5, and Fable 5.1 together, and stop burning Opus on work it was never needed for. the whole idea in one line: the strong model plans, the mid-tier model executes, Fable stays quiet until it's actually needed. roles, broken down: Opus 5.5, high effort, owns the plan and ships the final code Sonnet 5.5, medium effort, splits into explorer (reads the codebase), worker (edits files, runs tests), researcher (pulls docs) Fable 5.1, called through /advisor fable, reads everything happening in the session but stays silent unless something's actually wrong three moments where Fable speaks: → a plan goes out: is this actually the right call? → the same failure shows up again: is the search going nowhere? → the task gets marked finished: did something get skipped? Jev engineering does the same thing one level down. the forks that don't need real thought, which file, which tool, keep going or stop, go straight to Jev and come back in under half a second. the big models only ever see the forks that genuinely need a decision. anyone still running one model for everything is paying Opus prices to decide whether a file exists. drop this into Claude Code: "Rebuild my Claude Code setup around this structure: Look through ~/.claude/agents and .claude/agents for subagents already covering explorer, worker, and researcher. Only create new ones for roles that are missing. Set model: sonnet, effort: medium on each. If an existing subagent is locked to a different model, leave it as is and just list it. In ~/.claude/settings.json, set effortLevel to high and advisorModel to fable. Check for anything disabling the advisor, CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, or anything blocking feature-flag fetches, plus CLAUDE_CODE_EFFORT_LEVEL, which can override subagent effort settings. Report what you find. Don't change any of it yet. Add one line to ~/.claude/CLAUDE.md: check in with the advisor before a big plan, when the same error shows up twice, and before marking a long task done. Show every change as a diff first. Wait for my go-ahead before touching anything."

This is f*cking insane. This tip saved me thousands of dollars. run Opus 5.5, Sonnet 5.5, and Fable 5.1 together, and stop burning Opus on work it was never needed for. the whole idea in one line: the strong model plans, the mid-tier model executes, Fable stays quiet until it's actually needed. roles, broken down: Opus 5.5, high effort, owns the plan and ships the final code Sonnet 5.5, medium effort, splits into explorer (reads the codebase), worker (edits files, runs tests), researcher (pulls docs) Fable 5.1, called through /advisor fable, reads everything happening in the session but stays silent unless something's actually wrong three moments where Fable speaks: → a plan goes out: is this actually the right call? → the same failure shows up again: is the search going nowhere? → the task gets marked finished: did something get skipped? Jev engineering does the same thing one level down. the forks that don't need real thought, which file, which tool, keep going or stop, go straight to Jev and come back in under half a second. the big models only ever see the forks that genuinely need a decision. anyone still running one model for everything is paying Opus prices to decide whether a file exists. drop this into Claude Code: "Rebuild my Claude Code setup around this structure: Look through ~/.claude/agents and .claude/agents for subagents already covering explorer, worker, and researcher. Only create new ones for roles that are missing. Set model: sonnet, effort: medium on each. If an existing subagent is locked to a different model, leave it as is and just list it. In ~/.claude/settings.json, set effortLevel to high and advisorModel to fable. Check for anything disabling the advisor, CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, or anything blocking feature-flag fetches, plus CLAUDE_CODE_EFFORT_LEVEL, which can override subagent effort settings. Report what you find. Don't change any of it yet. Add one line to ~/.claude/CLAUDE.md: check in with the advisor before a big plan, when the same error shows up twice, and before marking a long task done. Show every change as a diff first. Wait for my go-ahead before touching anything."

rvaniaaa

252,291 просмотров • 11 дней назад

Claude Code tip: if Opus 5.5 is already your main model, Fable 5.1 has been sitting idle this whole time. wire it in with /advisor start it with /advisor fable Opus 5.5 writes every line. Fable 5.1 reads the whole session, every tool call, and says nothing until one of three moments: → a plan gets proposed: is this actually the right move, or just the first one? → the same error comes back twice: is the search stuck, or is this a dead end? → the task gets marked done: what got missed while it was moving fast? Opus 5.5 ships. Fable 5.1 catches what would've shipped broken. Jev engineering makes the same move one layer down: forks that don't need a real thinker, which file, which tool, retry or give up, get routed to Jev and answered in under half a second. the expensive model only ever sees the forks that genuinely split. the tree this runs on: > Opus 5.5, high effort, owns the main session > explorer, medium effort, reads the code > worker, medium effort, edits and runs tests > researcher, medium effort, pulls the docs > Fable 5.1 outside all of it, on call, never writing a line itself drop the tree and this prompt into Claude Code: "Rebuild my Claude Code setup around this tree: 1. Look in ~/.claude/agents and .claude/agents for subagents that already cover explorer, worker and researcher. Draft new ones only for roles that are missing. Set each to model: opus, effort: medium. If an existing subagent is pinned to a different model, list it, don't touch it. 2. Set the main session's effortLevel to high in ~/.claude/settings.json, and set advisorModel to fable. 3. Check for anything disabling the advisor: CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable blocking feature-flag fetches, and CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report what you find. Change nothing yet. 4. Add one line to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before marking a long task done. Show every change as a diff first. Don't touch anything until I say go."

Claude Code tip: if Opus 5.5 is already your main model, Fable 5.1 has been sitting idle this whole time. wire it in with /advisor start it with /advisor fable Opus 5.5 writes every line. Fable 5.1 reads the whole session, every tool call, and says nothing until one of three moments: → a plan gets proposed: is this actually the right move, or just the first one? → the same error comes back twice: is the search stuck, or is this a dead end? → the task gets marked done: what got missed while it was moving fast? Opus 5.5 ships. Fable 5.1 catches what would've shipped broken. Jev engineering makes the same move one layer down: forks that don't need a real thinker, which file, which tool, retry or give up, get routed to Jev and answered in under half a second. the expensive model only ever sees the forks that genuinely split. the tree this runs on: > Opus 5.5, high effort, owns the main session > explorer, medium effort, reads the code > worker, medium effort, edits and runs tests > researcher, medium effort, pulls the docs > Fable 5.1 outside all of it, on call, never writing a line itself drop the tree and this prompt into Claude Code: "Rebuild my Claude Code setup around this tree: 1. Look in ~/.claude/agents and .claude/agents for subagents that already cover explorer, worker and researcher. Draft new ones only for roles that are missing. Set each to model: opus, effort: medium. If an existing subagent is pinned to a different model, list it, don't touch it. 2. Set the main session's effortLevel to high in ~/.claude/settings.json, and set advisorModel to fable. 3. Check for anything disabling the advisor: CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable blocking feature-flag fetches, and CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report what you find. Change nothing yet. 4. Add one line to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before marking a long task done. Show every change as a diff first. Don't touch anything until I say go."

Ryven

35,757 просмотров • 12 дней назад

Claude Code feels completely different once you install this. Anthropic quietly released an official plugin called claude-code-setup and it basically turns Claude Code from “pretty good” into an actual AI dev environment. It scans your project and recommends: → hooks → skills → MCP servers → subagents → automations Then sets everything up step-by-step for you. Most people are using Claude Code completely vanilla… which is why their experience feels messy. The real power comes from the ecosystem around it. Install: /plugin install claude-code-setup@claude-plugins-official Bookmark this before you forget it.

Claude Code feels completely different once you install this. Anthropic quietly released an official plugin called claude-code-setup and it basically turns Claude Code from “pretty good” into an actual AI dev environment. It scans your project and recommends: → hooks → skills → MCP servers → subagents → automations Then sets everything up step-by-step for you. Most people are using Claude Code completely vanilla… which is why their experience feels messy. The real power comes from the ecosystem around it. Install: /plugin install claude-code-setup@claude-plugins-official Bookmark this before you forget it.

Suryansh Tiwari

1,551,606 просмотров • 4 месяцев назад

We just launched Claude Sonnet 4.5 and “Imagine with Claude”, a 5-day preview that creates dynamic experiences for you in real-time (and the first product I’ve worked on at Anthropic!). It pioneers the concept of “model-as-backend”, using a model to not only generate interfaces on the fly but also power all the functionality behind it – all made possible by our newest model, Claude Sonnet 4.5. Here’s a "choose your own adventure" version of my founder journey, as retold by Imagine with Claude:

We just launched Claude Sonnet 4.5 and “Imagine with Claude”, a 5-day preview that creates dynamic experiences for you in real-time (and the first product I’ve worked on at Anthropic!). It pioneers the concept of “model-as-backend”, using a model to not only generate interfaces on the fly but also power all the functionality behind it – all made possible by our newest model, Claude Sonnet 4.5. Here’s a "choose your own adventure" version of my founder journey, as retold by Imagine with Claude:

Sean Strong

115,727 просмотров • 1 год назад

$35 OF FREE CLAUDE OPUS 5 CREDITS FOR A WEEK, NO CARD ANYWHERE • the credit > Sign up with Google and the trial activates on its own, nothing to claim manually: > Opus 5 sits alongside Opus 4.8, Sonnet 4.6 and Haiku on the same key. > The window runs a week from activation. • wiring it up > base url: > model id: claude-opus-5 > In OpenCode Desktop hit Ctrl+, and add a custom provider with the id aerolink. > The same key drops into Codex, Cursor and Claude Code with nothing else changed. One key, not locked to one client -> every tool that takes a custom OpenAI-compatible endpoint reads it the same way. It routes through a third-party proxy rather than an official Anthropic channel, so keep client work off it ↓

$35 OF FREE CLAUDE OPUS 5 CREDITS FOR A WEEK, NO CARD ANYWHERE • the credit > Sign up with Google and the trial activates on its own, nothing to claim manually: > Opus 5 sits alongside Opus 4.8, Sonnet 4.6 and Haiku on the same key. > The window runs a week from activation. • wiring it up > base url: > model id: claude-opus-5 > In OpenCode Desktop hit Ctrl+, and add a custom provider with the id aerolink. > The same key drops into Codex, Cursor and Claude Code with nothing else changed. One key, not locked to one client -> every tool that takes a custom OpenAI-compatible endpoint reads it the same way. It routes through a third-party proxy rather than an official Anthropic channel, so keep client work off it ↓

slash1s

21,102 просмотров • 1 месяц назад

You don’t have to use one model (or one provider!) for everything. With Workshop, you can combine frontier and local models in the same workflow. For example: Opus can be the main agent, and delegate specific tasks to Gemma 4 via subagents. Better quality where it matters. Better privacy, speed, and cost where it counts. One workflow, best model for each task.

You don’t have to use one model (or one provider!) for everything. With Workshop, you can combine frontier and local models in the same workflow. For example: Opus can be the main agent, and delegate specific tasks to Gemma 4 via subagents. Better quality where it matters. Better privacy, speed, and cost where it counts. One workflow, best model for each task.

Workshop AI

1,023,720 просмотров • 5 месяцев назад

Fable 5 + Goose Ads is insane – literally a full ad-creative team right in Claude Code. 1. Install the skill: npx gooseworks install --all npx gooseworks login 2. Ask Claude Fable to make ads for your brand. /goose-ads create ads for my brand . Fable 5 pulls the ads already winning in your space and rebuilds them on-brand – your product, your palette, your copy – a whole batch, ready to test. It can ship a month of creative testing in a single prompt. This is also possible with Opus and Sonnet, but Fable's brand research is next level. Link below.

Shiv

223,176 просмотров • 3 месяцев назад

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

Alvaro Cintas

43,331 просмотров • 22 дней назад

Claude Code Scheduled Tasks is now available... here's a solid idea to connect it with Telegram Save this so you don't forget to set it up! First, ask Claude to add a simple Telegram messaging module to your repo. You can use the Telegram Bot Builder Skill from Link: Install command: npx claude-code-templates@latest --skill enterprise-communication/telegram-bot-builder Once the module is in your project, grab your bot credentials from BotFather and add the bot ID to your .env file That's it! ✅ Now every Scheduled Task you create should end with an instruction for Claude to send the task result to Telegram using that module. Claude will handle the delivery automatically on every task it runs

Claude Code Scheduled Tasks is now available... here's a solid idea to connect it with Telegram Save this so you don't forget to set it up! First, ask Claude to add a simple Telegram messaging module to your repo. You can use the Telegram Bot Builder Skill from Link: Install command: npx claude-code-templates@latest --skill enterprise-communication/telegram-bot-builder Once the module is in your project, grab your bot credentials from BotFather and add the bot ID to your .env file That's it! ✅ Now every Scheduled Task you create should end with an instruction for Claude to send the task result to Telegram using that module. Claude will handle the delivery automatically on every task it runs

Daniel San

91,123 просмотров • 7 месяцев назад

$200 to $20. That's how your AI costs will change if you switch from Claude Code Max to the MiniMax (official) Token Plan Plus in Kilo. MiniMax's latest model, M3, performs at 79% of Sonnet 5's level for a tenth of the price, and the plan gets you 1.7B tokens per month through Kilo. See how much you'd save with model freedom:

$200 to $20. That's how your AI costs will change if you switch from Claude Code Max to the MiniMax (official) Token Plan Plus in Kilo. MiniMax's latest model, M3, performs at 79% of Sonnet 5's level for a tenth of the price, and the plan gets you 1.7B tokens per month through Kilo. See how much you'd save with model freedom:

Kilo

25,441 просмотров • 3 месяцев назад

Progress on my spinning top battle game. Vibe-coding this with Claude Code, Opus 4.8 and using assets created with the Magnific MCP. Main improvements are the 3D models with the Magnific MCP. 1. 4 top varieties converted to 3D model. 2. Batle stadium 3D model. Also added new attacks, collisions, health bars, jump and dash buttons.

Progress on my spinning top battle game. Vibe-coding this with Claude Code, Opus 4.8 and using assets created with the Magnific MCP. Main improvements are the 3D models with the Magnific MCP. 1. 4 top varieties converted to 3D model. 2. Batle stadium 3D model. Also added new attacks, collisions, health bars, jump and dash buttons.

Jerrod Lew

13,874 просмотров • 4 месяцев назад

Unity just launched an official first-party plugin for Claude Code that unlocks 29 native Unity skills, supported CLI workflows and direct Editor control from a single install with no configuration required. → Available directly in the Claude Code plugin directory → 29 native Unity skills available at launch → One command to install, no configuration, officially supported by Unity

Unity just launched an official first-party plugin for Claude Code that unlocks 29 native Unity skills, supported CLI workflows and direct Editor control from a single install with no configuration required. → Available directly in the Claude Code plugin directory → 29 native Unity skills available at launch → One command to install, no configuration, officially supported by Unity

0xMarioNawfal

53,297 просмотров • 1 месяц назад

Introducing Time Machine for Claude Code Works in both Claude Desktop and Claude Code CLI /timemachine records your session as a timeline, including prompts, tool calls, edits, Bash commands, and turn endings Pick any point and fork from there, It restores both the conversation and the code state from that moment into a separate Git worktree and branch, while your original session stays untouched Install: npx claude-code-templates@latest --mod productivity/session-time-machine Then run: /reload-plugin /timemachine

Introducing Time Machine for Claude Code Works in both Claude Desktop and Claude Code CLI /timemachine records your session as a timeline, including prompts, tool calls, edits, Bash commands, and turn endings Pick any point and fork from there, It restores both the conversation and the code state from that moment into a separate Git worktree and branch, while your original session stays untouched Install: npx claude-code-templates@latest --mod productivity/session-time-machine Then run: /reload-plugin /timemachine

Daniel San

23,682 просмотров • 8 дней назад

Opus 4.8 is awesome but that's expected. The unsung hero of this release for me is dynamic workflows. Claude plans your task, fans it out to tens or hundreds of parallel subagents, verifies their work, and iterates until the results converge into one coordinated answer.

Opus 4.8 is awesome but that's expected. The unsung hero of this release for me is dynamic workflows. Claude plans your task, fans it out to tens or hundreds of parallel subagents, verifies their work, and iterates until the results converge into one coordinated answer.

Ado

153,209 просмотров • 4 месяцев назад