Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Pro tip: Do NOT run subagents at night, unless you have multiple subs. Especially with Opus 5.5 The main benefit of subagents is getting more done in less time, or a more thorough implementation. If your task is just a few hours long anyways, give it to Opus 5.5...

rohit3a's profile picture

rohit

1,350 subscribers

199,225 görüntüleme • 13 gün önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

I bet you didn't know that by default Codex only runs max 3 subagents concurrently. That's not ambitious enough for Astra. OpenAI tested Astra with up to 64 subagents. Copy this into your config.toml: [agents] max_concurrent_threads_per_session = 64 Astra orchestrating 64 Luna subagents in parallel is a sight to behold!
0:20

I bet you didn't know that by default Codex only runs max 3 subagents concurrently. That's not ambitious enough for Astra. OpenAI tested Astra with up to 64 subagents. Copy this into your config.toml: [agents] max_concurrent_threads_per_session = 64 Astra orchestrating 64 Luna subagents in parallel is a sight to behold!

Dan McAteer

111,166 görüntüleme • 2 ay önce

it's f*cking insane.. Anthropic just dropped a Claude Code setup that makes tokens up to 97% cheaper Opus brains, Sonnet bill: > Sonnet runs your session and writes the code > Haiku subagents grab the small tasks > Opus steps in only when Sonnet gets stuck > it checks the work, digs into the problem and puts Sonnet back on track $19.50 saved on every 1M tokens a Haiku 5.5 subagent writes, compared with Opus 5.5 one command sets it up: npx claude-code-templates@latest --setting model/sonnet-opus-advisor-haiku-subagents the easiest money you'll save on Claude Code this year
0:18

it's f*cking insane.. Anthropic just dropped a Claude Code setup that makes tokens up to 97% cheaper Opus brains, Sonnet bill: > Sonnet runs your session and writes the code > Haiku subagents grab the small tasks > Opus steps in only when Sonnet gets stuck > it checks the work, digs into the problem and puts Sonnet back on track $19.50 saved on every 1M tokens a Haiku 5.5 subagent writes, compared with Opus 5.5 one command sets it up: npx claude-code-templates@latest --setting model/sonnet-opus-advisor-haiku-subagents the easiest money you'll save on Claude Code this year

Mnimiy

55,980 görüntüleme • 26 gün önce

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: User, Project, or Local
0:17

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: User, Project, or Local

Daniel San

29,053 görüntüleme • 26 gün önce

Cursor now uses subagents to complete parts of a task in parallel. Subagents lead to faster overall execution and better context usage. They also let agents work on longer-running tasks. Also new: Cursor can generate images, ask clarifying questions, and more.
0:15

Cursor now uses subagents to complete parts of a task in parallel. Subagents lead to faster overall execution and better context usage. They also let agents work on longer-running tasks. Also new: Cursor can generate images, ask clarifying questions, and more.

Cursor

819,898 görüntüleme • 9 ay önce

Tasks can now spawn async subagents that move to the background and continue working independently, even if the main agent finishes its task and becomes inactive. This lets subagents handle long-running tasks, great for monitoring logs or waiting for builds.
0:17

Tasks can now spawn async subagents that move to the background and continue working independently, even if the main agent finishes its task and becomes inactive. This lets subagents handle long-running tasks, great for monitoring logs or waiting for builds.

Claude

349,890 görüntüleme • 10 ay önce

had Fable w/5.6-sol subagents clone WisprFlow if you have a spare machine with ~12gGiBs of vram, you can run this locally and serve it via tailscale to any device you own repo below
0:15

had Fable w/5.6-sol subagents clone WisprFlow if you have a spare machine with ~12gGiBs of vram, you can run this locally and serve it via tailscale to any device you own repo below

adi

42,628 görüntüleme • 3 ay önce

Updated the subagents system in my custom Pi extension to include: - Pi subagents - Codex subagents - Claude Code subagents The Pi thread can call and spin up any of them, and instead of just using the "codex exec" or whatever, it'll do a tool call that wraps it up in a first class way. Have a decent UI for them already added in as well. Pi being the main thread then having Codex/Claude Code as tools when needed feels so good. A flow I'm already using a ton is: "Implement feature ___, have a cc fable subagent research and plan out the api design + feature, then have a codex subagent implement it, then have a cc fable subagent do a review/fixes focused on simplicity and correctness" I also have a dynamic workflows extension setup and working, but it's not nearly as polished yet. Probably gonna make the subagent system more robust, then built it around that so u could have a workflow that flows between codex/cc/pi...
0:19

Updated the subagents system in my custom Pi extension to include: - Pi subagents - Codex subagents - Claude Code subagents The Pi thread can call and spin up any of them, and instead of just using the "codex exec" or whatever, it'll do a tool call that wraps it up in a first class way. Have a decent UI for them already added in as well. Pi being the main thread then having Codex/Claude Code as tools when needed feels so good. A flow I'm already using a ton is: "Implement feature ___, have a cc fable subagent research and plan out the api design + feature, then have a codex subagent implement it, then have a cc fable subagent do a review/fixes focused on simplicity and correctness" I also have a dynamic workflows extension setup and working, but it's not nearly as polished yet. Probably gonna make the subagent system more robust, then built it around that so u could have a workflow that flows between codex/cc/pi...

Ben Davis

25,712 görüntüleme • 3 ay önce

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.
0:12

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,269 görüntüleme • 5 ay önce

exploring subagent navigation ⦿ open sidebar with shortcut ⦿ search subagents ⦿ navigate between subagents ⦿ enter into a subagent
0:19

exploring subagent navigation ⦿ open sidebar with shortcut ⦿ search subagents ⦿ navigate between subagents ⦿ enter into a subagent

David Hill

13,278 görüntüleme • 11 ay önce

Cursor can now use multiple browsers at once with subagents.
0:15

Cursor can now use multiple browsers at once with subagents.

Cursor

299,780 görüntüleme • 9 ay önce

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.
0:18

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,046,048 görüntüleme • 6 ay önce

Incredibly excited today to launch file-based agents in Mastra! Add `instructions` as a .md file, a .ts file to `tools/` and the filename becomes the tool name, subagents in `subagents/`:
0:11

Incredibly excited today to launch file-based agents in Mastra! Add `instructions` as a .md file, a .ts file to `tools/` and the filename becomes the tool name, subagents in `subagents/`:

Sam Bhagwat

35,648 görüntüleme • 4 ay önce

This is GLM 5.2 creating and describing *images* How, since the model is text-only? With Amp's specialized subagents. Multi-modal agentic workflows at the pareto frontier of intelligence, speed, and cost.
0:23

This is GLM 5.2 creating and describing *images* How, since the model is text-only? With Amp's specialized subagents. Multi-modal agentic workflows at the pareto frontier of intelligence, speed, and cost.

Beyang

20,111 görüntüleme • 4 ay önce

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.
0:14

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,352 görüntüleme • 5 ay önce

Claude Code's new dynamic workflow is the real deal. 🤖 Why it matters: It's not just a chain of prompts — it's an autonomous agent swarm. 1. Set model to Opus 4.8 + reasoning effort /ultracode 2. Claude detects complexity, writes orchestration script on the fly 3. Spawns a parallel fleet of coordinated subagents Operator takeaway: This is the first time I've seen an agent actually decompose and delegate autonomously without a rigid framework. Have you tried it yet? 🚀
0:13

Claude Code's new dynamic workflow is the real deal. 🤖 Why it matters: It's not just a chain of prompts — it's an autonomous agent swarm. 1. Set model to Opus 4.8 + reasoning effort /ultracode 2. Claude detects complexity, writes orchestration script on the fly 3. Spawns a parallel fleet of coordinated subagents Operator takeaway: This is the first time I've seen an agent actually decompose and delegate autonomously without a rigid framework. Have you tried it yet? 🚀

EK

197,752 görüntüleme • 5 ay önce

Introducing /goal in Grok Build. Execute long-running tasks autonomously, with multiple rounds of subagents implementing and verifying a single goal.
0:10

Introducing /goal in Grok Build. Execute long-running tasks autonomously, with multiple rounds of subagents implementing and verifying a single goal.

Grok

4,228,293 görüntüleme • 4 ay önce

Jelly King: Opus 5.5 Mogged Astra, Fable and Sonnet In my jelly tests, Opus is in a league of its own right now. And it’s not just the wobble - the materials and detail are on another level too Look at this citrus slice. Glossy flesh, visible segments, soft folds when you pull it. Astra bends too, but those sharp creases look more like a crumpled wrapper than jelly Opus wins this one for me, and it’s cheaper. Maybe only Fable 5.5 can take the crown from Opus 👑 Estimated API cost: Opus 5.5 - $7.57 ChatGPT-6 Astra - $10.15 Would you still pay more for Astra after watching this? 👀
0:17

Jelly King: Opus 5.5 Mogged Astra, Fable and Sonnet In my jelly tests, Opus is in a league of its own right now. And it’s not just the wobble - the materials and detail are on another level too Look at this citrus slice. Glossy flesh, visible segments, soft folds when you pull it. Astra bends too, but those sharp creases look more like a crumpled wrapper than jelly Opus wins this one for me, and it’s cheaper. Maybe only Fable 5.5 can take the crown from Opus 👑 Estimated API cost: Opus 5.5 - $7.57 ChatGPT-6 Astra - $10.15 Would you still pay more for Astra after watching this? 👀

Vib3Coded

144,416 görüntüleme • 24 gün önce

Subagents are now available in Codex. You can accelerate your workflow by spinning up specialized agents to: • Keep your main context window clean • Tackle different parts of a task in parallel • Steer individual agents as work unfolds
0:12

Subagents are now available in Codex. You can accelerate your workflow by spinning up specialized agents to: • Keep your main context window clean • Tackle different parts of a task in parallel • Steer individual agents as work unfolds

OpenAI Developers

1,706,437 görüntüleme • 7 ay önce

One of the coolest things with Codex for Chrome is combining it with subagents so you can test things like multiplayer games! Available for both macOS and Windows. Happy Codexing
0:16

One of the coolest things with Codex for Chrome is combining it with subagents so you can test things like multiplayer games! Available for both macOS and Windows. Happy Codexing

dominik kundel

162,311 görüntüleme • 6 ay önce

an Anthropic engineer just showed a cleaner way to run Sonnet 5.5 + Opus 5.5 without wasting turns the expensive mistake is letting the wrong model stay in the loop too long. so I turned the routing logic into a prompt: → clear, scoped work stays on Sonnet 5.5 → failed checks trigger escalation → Opus gets a clean handoff, not the full transcript → cache stays warm whenever possible the numbers get weird fast: → 20K context: Opus is 1.88x per turn → 150K: 1.49x → 400K: 1.26x a late 300K switch costs $1.50 just to rebuild cache. the same handoff at 20K costs $0.10. the point is not to use Opus more. it is to make Claude prove when Opus is actually needed ↓ ↳
0:19

an Anthropic engineer just showed a cleaner way to run Sonnet 5.5 + Opus 5.5 without wasting turns the expensive mistake is letting the wrong model stay in the loop too long. so I turned the routing logic into a prompt: → clear, scoped work stays on Sonnet 5.5 → failed checks trigger escalation → Opus gets a clean handoff, not the full transcript → cache stays warm whenever possible the numbers get weird fast: → 20K context: Opus is 1.88x per turn → 150K: 1.49x → 400K: 1.26x a late 300K switch costs $1.50 just to rebuild cache. the same handoff at 20K costs $0.10. the point is not to use Opus more. it is to make Claude prove when Opus is actually needed ↓ ↳

fleyta

14,951 görüntüleme • 1 ay önce