Loading video...

Video Failed to Load

Go Home

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

iamdavidhill's profile picture

David Hill

21,224 subscribers

13,278 views • 10 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

We're having our first Claude Code Office Hours this Thursday @ 3pm PDT! Live streamed here on X from this account. On the agenda: - Talking subagents & announcing new subagent features with ! - Building an open source email agent using the Claude Code SDK
0:12

We're having our first Claude Code Office Hours this Thursday @ 3pm PDT! Live streamed here on X from this account. On the agenda: - Talking subagents & announcing new subagent features with ! - Building an open source email agent using the Claude Code SDK

Thariq

116,120 views • 1 year ago

💡 You can give subagents persistent memory via the "memory" field A subagent doesn't inherit the main session's auto memory, it forgets everything between runs. This field gives it its own dir across sessions Memory loads before starting & the agent writes back for next time
0:12

💡 You can give subagents persistent memory via the "memory" field A subagent doesn't inherit the main session's auto memory, it forgets everything between runs. This field gives it its own dir across sessions Memory loads before starting & the agent writes back for next time

Lydia Hallie ✨

73,609 views • 3 months ago

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

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 views • 18 days ago

subagents are just recursive agents where you can apply different prompts + models depending on the task. since they’re just a primitive, Cursor cli can actually spawn subagents by calling cursor-agent in headless mode via shell commands. that’s what makes the cli so nice. you can extend it, experiment, and have a lot of fun exploring orchestration patterns. here’s one way to do it w. dynamic model selection: 1. create a subagents.mdc rule 2. drop in: ``` --- alwaysApply: true --- ALWAYS spawn subagents by running `cursor-agent -p [task] --output-format=text --force --model [model]` in the terminal. Each subagent should return a summary of the changes it made. Subagents should be used for ALL tasks You can adopt a fan-out pattern where you spawn subagents to perform parallel isolated tasks, and then fan-in the results. Use the following models: - `--model gpt-5` for reasoning, researching, and planning - `--model sonnet-4` for implementation ``` 3. start cursor cli and try it out you can also adjust the rule to be more explicit when it should use subagents, when not to, which models when etc.
0:15

subagents are just recursive agents where you can apply different prompts + models depending on the task. since they’re just a primitive, Cursor cli can actually spawn subagents by calling cursor-agent in headless mode via shell commands. that’s what makes the cli so nice. you can extend it, experiment, and have a lot of fun exploring orchestration patterns. here’s one way to do it w. dynamic model selection: 1. create a subagents.mdc rule 2. drop in: ``` --- alwaysApply: true --- ALWAYS spawn subagents by running `cursor-agent -p [task] --output-format=text --force --model [model]` in the terminal. Each subagent should return a summary of the changes it made. Subagents should be used for ALL tasks You can adopt a fan-out pattern where you spawn subagents to perform parallel isolated tasks, and then fan-in the results. Use the following models: - `--model gpt-5` for reasoning, researching, and planning - `--model sonnet-4` for implementation ``` 3. start cursor cli and try it out you can also adjust the rule to be more explicit when it should use subagents, when not to, which models when etc.

eric zakariasson

57,554 views • 1 year ago

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 views • 9 months ago

Inspect your agent's session with /𝚝𝚛𝚊𝚌𝚎𝚜. Gain full visibility into prompts, tool calls, errors, cost, and subagent work directly from the terminal.
0:14

Inspect your agent's session with /𝚝𝚛𝚊𝚌𝚎𝚜. Gain full visibility into prompts, tool calls, errors, cost, and subagent work directly from the terminal.

eve

15,923 views • 2 months ago

Before adding another subagent ask what problem it's solving. A bloated system prompt is often the issue. Skills and tool search can fix that without splitting context across agents. My rule of thumb is to keep a subagent when the work is parallel, needs fresh context or one agent really can't pick the right tools. Otherwise, fold it into the main loop, turn its prompt into a skill, run your evals and keep whatever wins. Good write-up:
0:11

Before adding another subagent ask what problem it's solving. A bloated system prompt is often the issue. Skills and tool search can fix that without splitting context across agents. My rule of thumb is to keep a subagent when the work is parallel, needs fresh context or one agent really can't pick the right tools. Otherwise, fold it into the main loop, turn its prompt into a skill, run your evals and keep whatever wins. Good write-up:

Addy Osmani

74,331 views • 1 day ago

People losing so much tokens and have no idea about this: Subagent caches expire in five minutes. In Claude Code, a subagent that sits idle longer than 5 minutes loses its prompt cache. The next call rewrites the whole context from scratch and burns several times more tokens than a cache hit would. Anthropic's guide covers a single setting that stretches that window to an hour: "subagentPromptCacheTtl": "1h" The trade-off is in the write price. Each write to the 1-hour cache costs more than a write to the 5-minute one. You stop paying for a full rewrite every time a subagent pauses, though. For workflows with long gaps between subagent calls, the savings reportedly reach up to 25% of total token spend. Those savings depend heavily on how you work. If your subagents finish fast and rarely sit idle past five minutes, you pay the pricier write for nothing and your bill goes up. Check your own usage before you switch. A comparison script exists that estimates whether the 1-hour TTL saves you money or costs you more on your actual sessions. If your pauses stay under five minutes, keep the default.
0:14

People losing so much tokens and have no idea about this: Subagent caches expire in five minutes. In Claude Code, a subagent that sits idle longer than 5 minutes loses its prompt cache. The next call rewrites the whole context from scratch and burns several times more tokens than a cache hit would. Anthropic's guide covers a single setting that stretches that window to an hour: "subagentPromptCacheTtl": "1h" The trade-off is in the write price. Each write to the 1-hour cache costs more than a write to the 5-minute one. You stop paying for a full rewrite every time a subagent pauses, though. For workflows with long gaps between subagent calls, the savings reportedly reach up to 25% of total token spend. Those savings depend heavily on how you work. If your subagents finish fast and rarely sit idle past five minutes, you pay the pricier write for nothing and your bill goes up. Check your own usage before you switch. A comparison script exists that estimates whether the 1-hour TTL saves you money or costs you more on your actual sessions. If your pauses stay under five minutes, keep the default.

Robert Youssef

38,138 views • 15 days ago

Excited to share the new dynamic navigation center for WePresent—a simpler way to search, navigate, and save content. With and code by Lorenzo Migliorero
0:17

Excited to share the new dynamic navigation center for WePresent—a simpler way to search, navigate, and save content. With and code by Lorenzo Migliorero

Marvin Schwaibold

41,792 views • 2 years ago

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 views • 3 months ago

Codex is now more beautiful in Conductor! Codex tool calls now show richer file, command, and search details. We also now render Codex subagents and gpt-image-2 results.
0:12

Codex is now more beautiful in Conductor! Codex tool calls now show richer file, command, and search details. We also now render Codex subagents and gpt-image-2 results.

Charlie Holtz

46,346 views • 5 months ago

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 views • 4 months ago

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 views • 9 months ago

Starting a series called WordPress Explorations, where I explore far-out ideas for WordPress. First up: Pages & Layers sidebar—a persistent sidebar that keeps you oriented. No more diving in and out of the editor to navigate between pages.
0:18

Starting a series called WordPress Explorations, where I explore far-out ideas for WordPress. First up: Pages & Layers sidebar—a persistent sidebar that keeps you oriented. No more diving in and out of the editor to navigate between pages.

Rich Tabor

36,180 views • 11 months ago

Bug fixes shipping to Grok Build 0.2.13 (release notes will be available in the TUI and on change-log website) We are leveraging the alt-screen to better handle your background tasks, subagents, monitors with smart grouping allowing you to navigate between them quickly • Group Subagents → Tasks → Watchers, within subagents, order by agent type (Explore, General, Plan) • Show timestamps on pinned user messages at top of scrollback • Fix command highlighting when prompt has paste chips • Update the context-usage indicator to show tokens by default • ANSI16 fallback for themes • Better context usage breakdown/rendering • Update highlighting for /loop, monitor, tag colors • Tab now cycles Prompt → Scrollback → Tasks → Prompt • Order gateway turn-completion after streamed content • Formatting: fix language-tagged fenced code blocks and fix code under a list item
0:10

Bug fixes shipping to Grok Build 0.2.13 (release notes will be available in the TUI and on change-log website) We are leveraging the alt-screen to better handle your background tasks, subagents, monitors with smart grouping allowing you to navigate between them quickly • Group Subagents → Tasks → Watchers, within subagents, order by agent type (Explore, General, Plan) • Show timestamps on pinned user messages at top of scrollback • Fix command highlighting when prompt has paste chips • Update the context-usage indicator to show tokens by default • ANSI16 fallback for themes • Better context usage breakdown/rendering • Update highlighting for /loop, monitor, tag colors • Tab now cycles Prompt → Scrollback → Tasks → Prompt • Order gateway turn-completion after streamed content • Formatting: fix language-tagged fenced code blocks and fix code under a list item

skcd

15,075 views • 5 months ago

We’ve been spending way too much time on this sidebar with Paul Faivret . We re-structured the Interfere navigation, so we added this subtle animation to transition between the two layers.
0:10

We’ve been spending way too much time on this sidebar with Paul Faivret . We re-structured the Interfere navigation, so we added this subtle animation to transition between the two layers.

Jakub Krehel

74,194 views • 6 months ago

cursor can now read ur terminal in real time! we built a subagent to watch logs, training runs, security alerts, and step in to patch code with the cursor-cli
0:15

cursor can now read ur terminal in real time! we built a subagent to watch logs, training runs, security alerts, and step in to patch code with the cursor-cli

rajan agarwal

119,565 views • 1 year ago

in OpenCode v2 there is a new subagent/shell management ui you can see what's running and easily background or kill it
0:12

in OpenCode v2 there is a new subagent/shell management ui you can see what's running and easily background or kill it

dax

111,372 views • 4 months ago