Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

A viral Claude Code guide claims agent teams cut token use, but Anthropic's documentation says teams use significantly more tokens than a single session. → Agent teams are experimental and turn on with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1, and each teammate has its own context window → There is no --teammates flag: users... show more

0xMarioNawfal

266,075 subscribers

45,457 views • 7 hours ago •via X (Twitter)

Gaming Science & Technology

Anya Rossi• Live Now

Private livecam show

3 Comments

vøv △7 hours ago

1,683 forks for one task is pure chaos.

Maya6 hours ago

Agent teams ≠ token saver. Advisor is the real optimization move.

An Xuan6 hours ago

agent teams to save tokens is like hiring five people to save on salary

Related Videos

Claude Fable 5 is best used as an orchestrator that does the heavy reasoning and delegates token intensive but simpler tasks to cheaper models. 'fable-advisor' is your free and open-source plugin that does exactly that. New in fable-advisor: > A directive to Fable to minimize its own token usage (works surprisingly well) > GPT-5.5 as an implementer sub-agent via the Codex CLI (uses your ChatGPT sub so you don't pay extra) How to use it: 1. claude plugin marketplace add DannyMac180/fable-advisor && claude plugin install fable-advisor 2. /model fable

Claude Fable 5 is best used as an orchestrator that does the heavy reasoning and delegates token intensive but simpler tasks to cheaper models. 'fable-advisor' is your free and open-source plugin that does exactly that. New in fable-advisor: > A directive to Fable to minimize its own token usage (works surprisingly well) > GPT-5.5 as an implementer sub-agent via the Codex CLI (uses your ChatGPT sub so you don't pay extra) How to use it: 1. claude plugin marketplace add DannyMac180/fable-advisor && claude plugin install fable-advisor 2. /model fable

Dan McAteer

56,732 views • 3 months ago

Claude Code tip: once Opus 5.5 is your main model, stop leaving Fable 5.1 sitting idle put it on call with /advisor run /advisor fable Opus 5.5 keeps writing the code Fable 5.1 reads the full session, every tool call included, and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Fable 5.1 reviews. Opus 5.5 ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big model only sees the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: opus, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

Claude Code tip: once Opus 5.5 is your main model, stop leaving Fable 5.1 sitting idle put it on call with /advisor run /advisor fable Opus 5.5 keeps writing the code Fable 5.1 reads the full session, every tool call included, and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Fable 5.1 reviews. Opus 5.5 ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big model only sees the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: opus, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

delost

693,243 views • 6 days ago

Claude Code tip: once Opus 5.5 runs your main session, stop leaving Fable 5.1 on the bench put it on call with /advisor run /advisor fable Opus 5.5 keeps writing the code Fable 5.1 reads the whole session, every tool call included, and only speaks up at three moments: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Fable 5.1 reviews. Opus 5.5 ships jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to jev in under half a second, and the big model only sees the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: opus, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

Claude Code tip: once Opus 5.5 runs your main session, stop leaving Fable 5.1 on the bench put it on call with /advisor run /advisor fable Opus 5.5 keeps writing the code Fable 5.1 reads the whole session, every tool call included, and only speaks up at three moments: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Fable 5.1 reviews. Opus 5.5 ships jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to jev in under half a second, and the big model only sees the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: opus, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

Hanako

51,329 views • 4 days ago

Claude Code tip: keep Opus 5.5 as your main model, but stop paying Opus prices for your subagents move them to Sonnet 5.5 Opus 5.5 plans and decides Sonnet 5.5 subagents do the heavy reading, editing and testing at half the price ($2 / $10 vs $4 / $20 per 1M tokens) Fable 5.1 stays on call with /advisor and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Opus thinks. Sonnet does. Fable checks Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big models only see the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on Sonnet 5.5, medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: claude-sonnet-5-5, effort: medium > List any that pin a different model before changing them 2. Keep the main session on Opus, set effortLevel to high in ~/.claude/settings.json and advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

Claude Code tip: keep Opus 5.5 as your main model, but stop paying Opus prices for your subagents move them to Sonnet 5.5 Opus 5.5 plans and decides Sonnet 5.5 subagents do the heavy reading, editing and testing at half the price ($2 / $10 vs $4 / $20 per 1M tokens) Fable 5.1 stays on call with /advisor and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Opus thinks. Sonnet does. Fable checks Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big models only see the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on Sonnet 5.5, medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: claude-sonnet-5-5, effort: medium > List any that pin a different model before changing them 2. Keep the main session on Opus, set effortLevel to high in ~/.claude/settings.json and advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

delost

27,459 views • 3 days ago

Official Anthropic tip for Claude Code: stop burning Opus 5.5 on work Sonnet 5.5 can do, while Fable 5.1 sits idle hand the grunt work to Sonnet 5.5 subagents and put Fable 5.1 on call run /advisor fable Opus 5.5 plans and merges Sonnet 5.5 subagents read, edit and run the tests Fable 5.1 reads the full session and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Sonnet 5.5 builds. Fable 5.1 reviews. Opus 5.5 ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big models only see the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code on Sonnet 5.5 > worker edits and runs tests on Sonnet 5.5 > researcher pulls the docs on Sonnet 5.5 > all three on medium > Fable 5.1 on call for main and every subagent paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: sonnet, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

Official Anthropic tip for Claude Code: stop burning Opus 5.5 on work Sonnet 5.5 can do, while Fable 5.1 sits idle hand the grunt work to Sonnet 5.5 subagents and put Fable 5.1 on call run /advisor fable Opus 5.5 plans and merges Sonnet 5.5 subagents read, edit and run the tests Fable 5.1 reads the full session and only speaks up at three points: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Sonnet 5.5 builds. Fable 5.1 reviews. Opus 5.5 ships Jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to Jev in under half a second, and the big models only see the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code on Sonnet 5.5 > worker edits and runs tests on Sonnet 5.5 > researcher pulls the docs on Sonnet 5.5 > all three on medium > Fable 5.1 on call for main and every subagent paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: sonnet, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

delost

42,409 views • 2 days ago

Anthropic just revealed a trick to improve how Claude Opus 5.5 works. The idea is that Opus does the work while Fable 5.1 acts as a second opinion. All you have to do is open Claude Code and run: /advisor fable When Opus consults Fable, it gets the full context of the session, including the tools used and their results. It can be especially useful: → Before creating a large plan → When the same error keeps happening → Before marking a task as finished This gives you a second review without having to copy context between conversations. The feature is still experimental, requires access to Fable, and uses additional tokens. 🔖 Save this for your next session.

Anthropic just revealed a trick to improve how Claude Opus 5.5 works. The idea is that Opus does the work while Fable 5.1 acts as a second opinion. All you have to do is open Claude Code and run: /advisor fable When Opus consults Fable, it gets the full context of the session, including the tools used and their results. It can be especially useful: → Before creating a large plan → When the same error keeps happening → Before marking a task as finished This gives you a second review without having to copy context between conversations. The feature is still experimental, requires access to Fable, and uses additional tokens. 🔖 Save this for your next session.

Dean W. Perkins

48,271 views • 1 day ago

This is the best way to use Claude Fable in Claude Code without immediately hitting your limits. 1. Model set to Fable 5 2. Reasoning on Max 3. Instruct Claude to run a dynamic workflow where: 3a. Fable is the orchestrator 3b. Opus does the reasoning heavy phases Fable is so overpowered that you don't need its intelligence for every step. Let it orchestrate Opus or even Sonnet.

This is the best way to use Claude Fable in Claude Code without immediately hitting your limits. 1. Model set to Fable 5 2. Reasoning on Max 3. Instruct Claude to run a dynamic workflow where: 3a. Fable is the orchestrator 3b. Opus does the reasoning heavy phases Fable is so overpowered that you don't need its intelligence for every step. Let it orchestrate Opus or even Sonnet.

Dan McAteer

912,025 views • 3 months ago

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.

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 views • 1 month ago

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:

Avthar

10,754 views • 6 months ago

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

242,307 views • 2 days ago

opus 5 is getting routed to opus 5.2 tested opus 5 on xhigh with the same prompt in devin and claude code but results came out really different > claude code one is clean and more detailed > while devin one is almost there but not the same opus 5 in cc used to be lazy and hard to communicate with, but something changed in the last 2 days now it works for longer and is way easier to communicate with anthropic did same with fable release too where some users were being routed to fable 5.1 so it’s very likely opus 5 is getting routed to 5.2 in claude code can you guys tests and lemme know if it's getting routed for you or not?

opus 5 is getting routed to opus 5.2 tested opus 5 on xhigh with the same prompt in devin and claude code but results came out really different > claude code one is clean and more detailed > while devin one is almost there but not the same opus 5 in cc used to be lazy and hard to communicate with, but something changed in the last 2 days now it works for longer and is way easier to communicate with anthropic did same with fable release too where some users were being routed to fable 5.1 so it’s very likely opus 5 is getting routed to 5.2 in claude code can you guys tests and lemme know if it's getting routed for you or not?

J A Z I I

140,113 views • 20 days ago

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

Daniel San

57,445 views • 7 months ago

$120 OF CLAUDE OPUS 5 AND OPUS 4.8 ON A NEW ACCOUNT, NO CARD ANYWHERE • the credit > $100 on signup, $120 once a referral lands, plus a daily check-in bonus: > GitHub sign-in only now. > base url: • the four models > claude-opus-5 and claude-opus-5-thinking at $3/M in, $3/M out. > claude-opus-4-8 and claude-opus-4-8-thinking at $1/M in, $5/M out. > 1M context, OpenAI and Anthropic formats both accepted. Anthropic lists Opus 5 at $5 in and $25 out -> output at $3 here is eight times under that, which is the whole reason the balance goes as far as it does. Set the model to claude-opus-4-8 first. People are hitting 502s and missing-model errors on the opus-5 IDs, and latency sits at 16 to 19 seconds either way ↓

$120 OF CLAUDE OPUS 5 AND OPUS 4.8 ON A NEW ACCOUNT, NO CARD ANYWHERE • the credit > $100 on signup, $120 once a referral lands, plus a daily check-in bonus: > GitHub sign-in only now. > base url: • the four models > claude-opus-5 and claude-opus-5-thinking at $3/M in, $3/M out. > claude-opus-4-8 and claude-opus-4-8-thinking at $1/M in, $5/M out. > 1M context, OpenAI and Anthropic formats both accepted. Anthropic lists Opus 5 at $5 in and $25 out -> output at $3 here is eight times under that, which is the whole reason the balance goes as far as it does. Set the model to claude-opus-4-8 first. People are hitting 502s and missing-model errors on the opus-5 IDs, and latency sits at 16 to 19 seconds either way ↓

slash1s

13,400 views • 1 month ago

We recreated this video with Opus 5.5 in ChatCut. Give it a reference and build your own version on a real, editable timeline. Use the ChatCut plugin for Claude Code or our desktop app. Free with your existing Claude subscription!

We recreated this video with Opus 5.5 in ChatCut. Give it a reference and build your own version on a real, editable timeline. Use the ChatCut plugin for Claude Code or our desktop app. Free with your existing Claude subscription!

ChatCut

15,610 views • 12 days ago

After Weeks Of Astra I Can Confirm Fable 5.1 > Astra Astra is a solid model, but lacks usage.. You can burn through weekly usage in 1 day of a $200 Pro Plan. Claude is actually better for usage + intelligence. Upcoming Opus 5.2 will shift focus back to Claude. OpenAI has gained traction and immediately backtracked by canceling new PRO plans. Astra is better in areas like 3D / Computer Use However the stronger model and service is with Claude. Running Fable 5.1 main orchestrator with Opus 5 / Astra workers is the meta.

After Weeks Of Astra I Can Confirm Fable 5.1 > Astra Astra is a solid model, but lacks usage.. You can burn through weekly usage in 1 day of a $200 Pro Plan. Claude is actually better for usage + intelligence. Upcoming Opus 5.2 will shift focus back to Claude. OpenAI has gained traction and immediately backtracked by canceling new PRO plans. Astra is better in areas like 3D / Computer Use However the stronger model and service is with Claude. Running Fable 5.1 main orchestrator with Opus 5 / Astra workers is the meta.

Eric ⚡️ Building...

18,120 views • 17 days ago

I built a form-filling agent that anyone can use 💫 This is an extremely simple but useful (I hope) app. Upload a fillable form 📋, some context files, and chat with the agent to fill the form out automatically ✍️ 1️⃣ Yes it is a Claude Code SDK wrapper 2️⃣ It is better and faster than ChatGPT/Claude UI out of the box 3️⃣ We use LlamaParse to parse the context files, so you can have more trust that we are able to read context without hallucinations (e.g. messy scanned handwriting, drivers license photo, and more). This was one of my holiday Claude Code vibe-coding projects. Built with Opus 4.5, and also powered by Opus 4.5. Feeling the AGI 🫡 App is here: Repo is open-source:

I built a form-filling agent that anyone can use 💫 This is an extremely simple but useful (I hope) app. Upload a fillable form 📋, some context files, and chat with the agent to fill the form out automatically ✍️ 1️⃣ Yes it is a Claude Code SDK wrapper 2️⃣ It is better and faster than ChatGPT/Claude UI out of the box 3️⃣ We use LlamaParse to parse the context files, so you can have more trust that we are able to read context without hallucinations (e.g. messy scanned handwriting, drivers license photo, and more). This was one of my holiday Claude Code vibe-coding projects. Built with Opus 4.5, and also powered by Opus 4.5. Feeling the AGI 🫡 App is here: Repo is open-source:

Jerry Liu

48,466 views • 9 months ago

$ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.$

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.

Yarchi

462,780 views • 3 months ago

Anthropic's Claude Opus 5 can reason through legal work where the answer depends on the substance of each document, who received it, when it was created, and how it relates to the rest of the production set. In this Box Agent demo, Opus 5 reviews 14 documents against a privilege protocol and discovery requests, catches a possible waiver, separates a privileged email from its producible attachment, identifies one sentence that should be redacted, and saves a cited review and draft privilege log back to Box for supervising counsel. Customers can use Claude Opus 5 in Box AI Studio to build custom agents for their own document-heavy legal workflows.

Anthropic's Claude Opus 5 can reason through legal work where the answer depends on the substance of each document, who received it, when it was created, and how it relates to the rest of the production set. In this Box Agent demo, Opus 5 reviews 14 documents against a privilege protocol and discovery requests, catches a possible waiver, separates a privileged email from its producible attachment, identifies one sentence that should be redacted, and saves a cited review and draft privilege log back to Box for supervising counsel. Customers can use Claude Opus 5 in Box AI Studio to build custom agents for their own document-heavy legal workflows.

Box

1,693,975 views • 2 months ago

🚨 INTRODUCING THE ABACUS AI SUPERCOMPUTER - literally build ANY cloud service with a prompt - host open-source LLMs & always-on agents - bring your own Codex, Claude or Anti-gravity - multi-agent architectures with Opus 4.8 and GPT 5.5 - run 3D games or any other server at scale - connect git and collaborate with teams Build a billion dollar business by simply prompting in english!!

🚨 INTRODUCING THE ABACUS AI SUPERCOMPUTER - literally build ANY cloud service with a prompt - host open-source LLMs & always-on agents - bring your own Codex, Claude or Anti-gravity - multi-agent architectures with Opus 4.8 and GPT 5.5 - run 3D games or any other server at scale - connect git and collaborate with teams Build a billion dollar business by simply prompting in english!!

Abacus.AI

11,928,804 views • 4 months ago

Cline has shipped Cline SDK, an open-source agent runtime that now powers the CLI, VS Code, JetBrains, and Kanban, and is available for any team to build on. The whole Cline product line is being migrated onto it. > Cline CLI scores 74.2% on Terminal Bench 2.0 with claude-opus-4.7, ahead of Claude Code at 69.4%. > Stateless loop, stateful orchestration, and provider layer as separate packages. > Agent teams, plugins, MCP, CRON jobs, and connector channels for Telegram, Slack, WhatsApp, all native.

Cline has shipped Cline SDK, an open-source agent runtime that now powers the CLI, VS Code, JetBrains, and Kanban, and is available for any team to build on. The whole Cline product line is being migrated onto it. > Cline CLI scores 74.2% on Terminal Bench 2.0 with claude-opus-4.7, ahead of Claude Code at 69.4%. > Stateless loop, stateful orchestration, and provider layer as separate packages. > Agent teams, plugins, MCP, CRON jobs, and connector channels for Telegram, Slack, WhatsApp, all native.

🚨 AI News | TestingCatalog

12,063 views • 4 months ago