Skip to content

docs: stream subagent tool calls #7280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dianed-square merged 1 commit into from
Feb 17, 2026
Merged

docs: stream subagent tool calls #7280

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion documentation/docs/guides/subagents.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ sidebar_position: 50
sidebar_label: Subagents
---

Subagents are independent instances that execute tasks while keeping your main conversation clean and focused. They bring process isolation and context preservation by offloading work to separate instances. Think of them as temporary assistants that handle specific jobs without cluttering your chat with tool execution details.
Subagents are independent instances that execute tasks while keeping your main conversation clean and focused. Think of them as temporary assistants that handle specific jobs, bringing process isolation and context preservation by offloading work to separate instances.

<details>
<summary>Subagents Walkthrough</summary>
Expand Down Expand Up @@ -39,6 +39,12 @@ You can run multiple subagents sequentially or in parallel.
| **Sequential** (Default) | Tasks execute one after another | "first...then", "after" | `"First analyze the code, then generate documentation"` |
| **Parallel** | Tasks execute simultaneously | "parallel", "simultaneously", "at the same time", "concurrently" | `"Create three HTML templates in parallel"` |

While subagents are working, a record of their tool calls appears in the `Logs` section of the subagent call in goose Desktop or is printed in the goose CLI output. For example:

```text
[subagent:16] text_editor | developer
Copy link

Copilot AI Feb 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CLI rendering includes a leading "▸" (and indentation) before the "[subagent:…]" header, so this example should either include that prefix or clarify that it’s showing only the inner header text (e.g., JSON stream mode).

Suggested change
[subagent:16] text_editor | developer
▸ [subagent:16] text_editor | developer

Copilot uses AI. Check for mistakes.
Copy link
Contributor Author

@dianed-square dianed-square Feb 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just showed the text portion of the log used by both CLI/UI

```

:::info
If a subagent fails or times out (5-minute default), you will receive no output from that subagent. For parallel execution, if any subagent fails, you get results only from the successful ones.
:::
Expand Down
Loading