Skip to content

small blog fixes #3549

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
angiejones merged 1 commit into from
Jul 27, 2025
Merged

small blog fixes #3549

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: 4 additions & 4 deletions documentation/blog/2025-07-21-orchestrating-subagents/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ You're probably wondering how I got here.

<!--truncate-->

Before I explain, it’s better if I just show you:
Before I explain, it’s better if I just show you.

👉Try it yourself: https://api-playground-production.up.railway.app/

Expand Down Expand Up @@ -58,14 +58,14 @@ export GOOSE_ALPHA_FEATURES=true

## Instructing My Team

There are a few ways to create subagents in Goose. You can use natural language prompts, define them through [recipes](/docs/guides/recipes/), or even spin up [external subagents](/docs/experimental/subagents/#external-subagents) like Codex or Claude Code..
There are a few ways to create subagents in Goose. You can use natural language prompts, define them through [recipes](/docs/guides/recipes/), or even spin up [external subagents](/docs/experimental/subagents/#external-subagents) like Codex or Claude Code.

I took the natural language prompt approach because it felt convenient to directly configure a subagent through one prompt. Here’s the prompt I used:

```
Build a real-time collaborative API testing platform using 3 AI subagents working sequentially - like "Google Docs for Postman" where teams can test APIs together, but for kids. Make it so errors and results are explained in a way that kids can understand and the design is kid friendly using metaphors.

3 Sequential subagents
3 Sequential Subagents

- Subagent 1: Create a WebSocket backend server that handles API request execution (GET/POST/PUT/DELETE with headers, body, auth) AND real-time collaboration features (multiple users, shared collections, live updates).

Expand All @@ -83,7 +83,7 @@ Build a real-time collaborative API testing platform using 3 AI subagents workin

Final result should be a working web app where multiple people can test APIs together, see each other's requests and responses instantly, and collaborate without conflicts. Use HTML/CSS/JS for the frontend, no frameworks.

Set the time out to 9 minutes
Set the time out to 9 minutes.
```

:::note TLDR
Expand Down