正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Opus 4.6 lets you set the effort level Not every task needs high reasoning. For simpler tasks you can set it to low or medium. Claude thinks less (or skips it entirely), makes fewer tool calls, and gives more concise answers Lower effort = faster responses with fewer tokens!

Lydia Hallie ✨

136,633 subscribers

34,866 次观看 • 8 个月前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Opus 5.5 works best on 'low' reasoning effort. I ran some tests as part of a project I'm working on. Opus 5.5 on 'low' reasoning vs. 'max' was at parity on task completion but 12x lower cost! Set 'low' reasoning effort by default and increase it for the hardest problems.

Opus 5.5 works best on 'low' reasoning effort. I ran some tests as part of a project I'm working on. Opus 5.5 on 'low' reasoning vs. 'max' was at parity on task completion but 12x lower cost! Set 'low' reasoning effort by default and increase it for the hardest problems.

Dan McAteer

124,009 次观看 • 1 个月前

Sonnet 5.5 is here! In Claude Code, users get ~30% more tasks done compared to Sonnet 5. It's smarter, so it needs fewer tokens for the same work. Here it rakes a yard of leaves using tool calls. 24s faster than Sonnet 5, with 6K fewer tokens. It leaves her extra time to read :)

Sonnet 5.5 is here! In Claude Code, users get ~30% more tasks done compared to Sonnet 5. It's smarter, so it needs fewer tokens for the same work. Here it rakes a yard of leaves using tool calls. 24s faster than Sonnet 5, with 6K fewer tokens. It leaves her extra time to read :)

cat

48,305 次观看 • 26 天前

Gemini 3.6 Flash is available in Antigravity CLI ☄️ Set it via /model which also now has an effort level slider! Recommend using medium effort for most tasks. Give it a try and let us know what you think. 🙏

Gemini 3.6 Flash is available in Antigravity CLI ☄️ Set it via /model which also now has an effort level slider! Recommend using medium effort for most tasks. Give it a try and let us know what you think. 🙏

Jack Wotherspoon

21,897 次观看 • 3 个月前

ANTHROPIC JUST DROPPED THE OFFICIAL GUIDE TO PROMPTING OPUS 5 This is the most important prompting guide for anyone using Claude. Bookmark this before you forget. Most people still prompt Opus 5 like older models. That's the mistake. > give the complete task upfront — don't drip-feed instructions. > explicitly ask for shorter responses if you want them. > use low/medium effort by default. increase effort only when needed. > let it finish the entire feature instead of asking for partial implementations. > use subagents intentionally for large codebases, not every task. Opus 5 is at its best when you stop micromanaging it and let it own the work. Read it before writing your next prompt. Claude → Opus 5 → Agentic Execution → Production-Ready Output → Money

ANTHROPIC JUST DROPPED THE OFFICIAL GUIDE TO PROMPTING OPUS 5 This is the most important prompting guide for anyone using Claude. Bookmark this before you forget. Most people still prompt Opus 5 like older models. That's the mistake. > give the complete task upfront — don't drip-feed instructions. > explicitly ask for shorter responses if you want them. > use low/medium effort by default. increase effort only when needed. > let it finish the entire feature instead of asking for partial implementations. > use subagents intentionally for large codebases, not every task. Opus 5 is at its best when you stop micromanaging it and let it own the work. Read it before writing your next prompt. Claude → Opus 5 → Agentic Execution → Production-Ready Output → Money

Rahul

408,213 次观看 • 2 个月前

jev + sonnet 5.5 is f**king insane. my entire workflow got 4x faster after adding these 6 lines to CLAUDE.md. [with jev connected, paste this👇] 1. Before you start a Claude worker, ask Jev once to select a host-approved profile with one or two sessions. The profile must specify each session’s model and effort level. If Jev makes no selection, use the host default. 2. The host must check Jev’s selection. The host must set the model and effort before each session starts. Keep these settings fixed during the session. The host controls permissions and approvals. 3. Use Sonnet 5.5 at medium effort for clear coding tasks. Use higher effort for complex reasoning or JSON tasks. Use a second Claude only for independent research or a review that the user requested. 4. Give the second Claude the task, applicable files, limits, and completion requirements. Return its findings and evidence to the lead. 5. Complete the requested work. Ask the user only when you cannot continue without input or before an action that needs approval. Do not add features, tests, files, documentation, refactors, or review rounds that the user did not request. When the work is complete and checked, stop. Report the result. 6. Before you report completion, run a test, build, type check, or command that checks the code change. If no check can run, identify the missing check. Explain why it cannot run. same task. two timers. watch the difference.

Avid

177,380 次观看 • 26 天前

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

36,121 次观看 • 23 天前

I’ve been using Claude Code’s Concise Output Style and it makes the experience much cleaner I’d combine it with these settings: - Output Style: Concise Straight to the answer, no preambles or unnecessary narration - spinnerTipsEnabled: false No tips while Claude is thinking - awaySummaryEnabled: false No recap when you return to the terminal - verbose: false Keeps commands and tool calls compact Claude Code feels much less noisy

I’ve been using Claude Code’s Concise Output Style and it makes the experience much cleaner I’d combine it with these settings: - Output Style: Concise Straight to the answer, no preambles or unnecessary narration - spinnerTipsEnabled: false No tips while Claude is thinking - awaySummaryEnabled: false No recap when you return to the terminal - verbose: false Keeps commands and tool calls compact Claude Code feels much less noisy

Daniel San

36,725 次观看 • 2 个月前

Jev + Opus 5.5 is the most underrated setup in AI right now, and i don't get why nobody's talking about it. I stopped letting Opus make every small decision in my agents. Jev makes them now. My Opus bill dropped ~500% on the same tasks, same results. Here's what Jev handles: - which files and notes to load before Opus sees anything - which effort level each task actually needs - what to do when a tool fails - which tests to run, and when to stop Opus only gets called for the hard reasoning. Every decision is a typed result the host checks before it runs. The exact prompt to set this up in your workflow is below.

Jev + Opus 5.5 is the most underrated setup in AI right now, and i don't get why nobody's talking about it. I stopped letting Opus make every small decision in my agents. Jev makes them now. My Opus bill dropped ~500% on the same tasks, same results. Here's what Jev handles: - which files and notes to load before Opus sees anything - which effort level each task actually needs - what to do when a tool fails - which tests to run, and when to stop Opus only gets called for the hard reasoning. Every decision is a typed result the host checks before it runs. The exact prompt to set this up in your workflow is below.

Anatoli Kopadze

77,128 次观看 • 27 天前

You can now quickly eval GPT-5 and reasoning efforts across your existing responses. With the built-in grader, compare responses to find the best model and reasoning effort for you. ⚡️👀

You can now quickly eval GPT-5 and reasoning efforts across your existing responses. With the built-in grader, compare responses to find the best model and reasoning effort for you. ⚡️👀

OpenAI Developers

79,960 次观看 • 1 年前

we just made Claude Code - use 53% fewer tokens - respond 48% faster - give 3.2x better responses just by giving it a better grep

we just made Claude Code - use 53% fewer tokens - respond 48% faster - give 3.2x better responses just by giving it a better grep

Aamir

910,937 次观看 • 11 个月前

This is amazing. Do this: 1. Set model to Opus 4.8 2. Reasoning effort to /ultracode Enables Claude Code's new Dynamic Workflows. Claude will autonomously detect complex tasks, write an orchestration script, and spawn an agent swarm.

This is amazing. Do this: 1. Set model to Opus 4.8 2. Reasoning effort to /ultracode Enables Claude Code's new Dynamic Workflows. Claude will autonomously detect complex tasks, write an orchestration script, and spawn an agent swarm.

Dan McAteer

879,790 次观看 • 4 个月前

PEOPLE ARE BURNING THROUGH THEIR TOKENS IN 30 MINUTES AND BLAMING CLAUDE The problem isn’t with the model. The problem is how they’re using it A simple formatting question they set Max effort The 40th message in the chat the model re-reads the entire history from the beginning Every single time. Using your tokens Low effort costs 10 times less than Max Just get into the habit of routing tasks by level and your limit won’t run out by noon Tokens don’t disappear. You’re just paying for unnecessary processing

PEOPLE ARE BURNING THROUGH THEIR TOKENS IN 30 MINUTES AND BLAMING CLAUDE The problem isn’t with the model. The problem is how they’re using it A simple formatting question they set Max effort The 40th message in the chat the model re-reads the entire history from the beginning Every single time. Using your tokens Low effort costs 10 times less than Max Just get into the habit of routing tasks by level and your limit won’t run out by noon Tokens don’t disappear. You’re just paying for unnecessary processing

Asteri

15,752 次观看 • 4 个月前

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,681 次观看 • 6 个月前

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.

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,702,864 次观看 • 1 个月前

Do more. Effort less. Apple Intelligence makes studying simpler than ever with Writing Tools.

Do more. Effort less. Apple Intelligence makes studying simpler than ever with Writing Tools.

Apple

6,460,550 次观看 • 1 年前

Codex users: do this right *now*. Max reasoning effort is off by default. Luna at Max reasoning is ~ Sol Medium / Opus 5 Medium level at 1/6th the cost. Change your life today.

Codex users: do this right now. Max reasoning effort is off by default. Luna at Max reasoning is ~ Sol Medium / Opus 5 Medium level at 1/6th the cost. Change your life today.

Dan McAteer

1,144,841 次观看 • 2 个月前

🚨 THIS IS INSANE 🚨 Someone already shared Fable 5.1 optimizations you can start to use "NOW". Here I show you how you can use them: 👇 1. Set effort to 'low' 2. Run '/claude-api cost-optimize' 3. Run 'claude-api prompt-audit' 4. Change effort mid-conversation w/o cache hit 5. Update Fable 5.1 API config w/ 'claude-api migrate' Bookmark this, you will need it 🔖

🚨 THIS IS INSANE 🚨 Someone already shared Fable 5.1 optimizations you can start to use "NOW". Here I show you how you can use them: 👇 1. Set effort to 'low' 2. Run '/claude-api cost-optimize' 3. Run 'claude-api prompt-audit' 4. Change effort mid-conversation w/o cache hit 5. Update Fable 5.1 API config w/ 'claude-api migrate' Bookmark this, you will need it 🔖

alex

44,986 次观看 • 1 个月前

Introducing Span-02: anytime reasoning for decisions. Reasoning models make you pick an effort level and wait. Span-02 takes a deadline and always returns its best decision so far. It gets better the longer it thinks. With reasoning off, it beats Jev at 1/4 of the price, and runs at 1/3 the latency of decision models at its level. It can: - Answer with numbers and scores, not just probabilities and choices - See images and screens (multimodal) - Take a configurable reasoning time And it’s fully open weight!

Introducing Span-02: anytime reasoning for decisions. Reasoning models make you pick an effort level and wait. Span-02 takes a deadline and always returns its best decision so far. It gets better the longer it thinks. With reasoning off, it beats Jev at 1/4 of the price, and runs at 1/3 the latency of decision models at its level. It can: - Answer with numbers and scores, not just probabilities and choices - See images and screens (multimodal) - Take a configurable reasoning time And it’s fully open weight!

Respan

217,916 次观看 • 9 天前

The model picker got a little facelift. Star your favorites. Dial the thinking up (or down) with effort controls. Because not every task needs max brainpower.

The model picker got a little facelift. Star your favorites. Dial the thinking up (or down) with effort controls. Because not every task needs max brainpower.

Notion

37,907 次观看 • 2 个月前