docs: remove subagents from experimental (#4907)

This commit is contained in:
dianed-square
2025-09-30 19:32:48 -07:00
committed by GitHub
parent f2bf927011
commit 937c75bc51
31 changed files with 42 additions and 55 deletions
+1 -1
View File
@@ -1,5 +1,5 @@
---
sidebar_position: 25
sidebar_position: 105
title: Using Goose in ACP Clients
sidebar_label: Goose in ACP Clients
---
+1 -1
View File
@@ -1,5 +1,5 @@
---
sidebar_position: 19
sidebar_position: 90
title: Goose Extension Allowlist
sidebar_label: Extension Allowlist
---
+1 -1
View File
@@ -1,5 +1,5 @@
---
sidebar_position: 8
sidebar_position: 45
title: CLI Providers
sidebar_label: CLI Providers
description: Use Claude Code, Cursor Agent, or Gemini CLI subscriptions in Goose
+2 -2
View File
@@ -1,5 +1,5 @@
---
sidebar_position: 15
sidebar_position: 85
title: Configuration File
sidebar_label: Configuration File
---
@@ -47,7 +47,7 @@ These settings enable experimental features that are in active development. Thes
| Setting | Purpose | Values | Default | Required |
|---------|---------|---------|---------|-----------|
| `ALPHA_FEATURES` | Enables experimental alpha features like [subagents](/docs/experimental/subagents) | true/false | false | No |
| `ALPHA_FEATURES` | Enables access to experimental alpha features—check the feature docs to see if this flag is required | true/false | false | No |
Additional [environment variables](/docs/guides/environment-variables) may also be supported in config.yaml.
@@ -2,6 +2,7 @@
title: Enhanced Code Editing with AI Models
sidebar_label: Enhanced Code Editing
description: Use AI models to intelligently apply code changes
sidebar_position: 110
---
The [Developer extension](/docs/mcp/developer-mcp) supports using AI models for enhanced code editing through the `str_replace` command. When configured, it intelligently applies code changes using an AI model instead of simple string replacement.
@@ -1,5 +1,5 @@
---
sidebar_position: 20
sidebar_position: 95
title: Environment Variables
sidebar_label: Environment Variables
---
@@ -319,7 +319,7 @@ These variables enable experimental features that are in active development. The
| Variable | Purpose | Values | Default |
|----------|---------|---------|---------|
| `ALPHA_FEATURES` | Enables experimental alpha features like [subagents](/docs/experimental/subagents) | "true", "1" (case insensitive) to enable | false |
| `ALPHA_FEATURES` | Enables experimental alpha features—check the feature docs to see if this flag is required | "true", "1" (case insensitive) to enable | false |
**Examples**
+1 -1
View File
@@ -1,6 +1,6 @@
---
title: File Access and Management
sidebar_position: 10
sidebar_position: 70
sidebar_label: File Management
description: Efficiently find and reference files in Goose Desktop and follow best practices for safe file operations
---
@@ -1,5 +1,5 @@
---
sidebar_position: 7
sidebar_position: 35
title: CLI Commands
sidebar_label: CLI Commands
toc_max_heading_level: 4
@@ -1,5 +1,5 @@
---
sidebar_position: 6
sidebar_position: 25
title: Goose Permission Modes
sidebar_label: Goose Permissions
---
@@ -1,7 +1,7 @@
---
title: Set LLM Rate Limits
sidebar_label: LLM Rate Limits
sidebar_position: 9
sidebar_position: 60
---
import Tabs from '@theme/Tabs';
@@ -1,6 +1,6 @@
{
"label": "Rich Interactive Chat",
"position": 8,
"position": 55,
"link": {
"type": "doc",
"id": "guides/interactive-chat/index"
+1 -1
View File
@@ -1,7 +1,7 @@
---
title: Goose Logging System
sidebar_label: Logging System
sidebar_position: 9
sidebar_position: 65
---
@@ -1,5 +1,5 @@
---
sidebar_position: 3
sidebar_position: 15
title: Managing Projects
sidebar_label: Managing Projects
---
@@ -1,6 +1,6 @@
{
"label": "Managing Tools",
"position": 4,
"position": 15,
"link": {
"type": "doc",
"id": "guides/managing-tools/index"
@@ -1,5 +1,5 @@
{
"label": "Multi-Model Config",
"position": 20,
"position": 100,
"description": "Configure multiple models and providers for model-switching strategies."
}
@@ -1,6 +1,6 @@
{
"label": "Recipes",
"position": 2,
"position": 5,
"link": {
"type": "doc",
"id": "guides/recipes/index"
+1 -1
View File
@@ -1,5 +1,5 @@
---
sidebar_position: 13
sidebar_position: 75
title: Running Tasks
sidebar_label: Run Tasks
---
+268
View File
@@ -0,0 +1,268 @@
---
title: Subagents
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.
## How to Use Subagents
To use subagents, ask Goose to delegate tasks using natural language. Goose automatically decides when to spawn subagents and handles their lifecycle. You can:
1. **Request specialized help**: "Use a code reviewer to analyze this function for security issues"
2. **Reference specific recipes**: "Use the 'security-auditor' recipe to scan this endpoint"
3. **Run parallel tasks**: "Create three HTML templates simultaneously"
4. **Delegate complex work**: "Research quantum computing developments and summarize findings"
You can run multiple subagents sequentially or in parallel.
| Type | Description | Trigger Keywords | Example |
|------|-------------|------------------|---------|
| **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"` |
:::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.
:::
## Internal Subagents
Internal subagents spawn Goose instances to handle tasks using your current session's context and extensions. There are two ways to configure and execute internal subagents:
1. **Direct Prompts** - Quick, one-off tasks using natural language instructions
2. **Recipes** - Reusable, structured configurations for specialized subagent behavior
### Direct Prompts
Direct prompts provided for one-off tasks using natural language prompts. The main agent automatically configures the subagent based on your request.
**Goose Prompt:**
```
"Use 2 subagents to create hello.html with 'Hello World' content and goodbye.html with 'Goodbye World' content in parallel"
```
**Tool Output:**
```json
{
"execution_summary": {
"total_tasks": 2,
"successful_tasks": 2,
"failed_tasks": 0,
"execution_time_seconds": 16.2
},
"task_results": [
{
"task_id": "create_hello_html",
"status": "success",
"result": "Successfully created hello.html with Hello World content"
},
{
"task_id": "create_goodbye_html",
"status": "success",
"result": "Successfully created goodbye.html with Goodbye World content"
}
]
}
```
### Recipes
Use [recipe](/docs/guides/recipes/) files to define specific instructions, extensions, and behavior for subagents. Recipes provide reusable configurations that can be shared and referenced by name.
**Creating a Recipe File**
`code-reviewer.yaml`
```yaml
id: code-reviewer
version: 1.0.0
title: "Code Review Assistant"
description: "Specialized subagent for code quality and security analysis"
instructions: |
You are a code review assistant. Analyze code and provide feedback on:
- Code quality and readability
- Security vulnerabilities
- Performance issues
- Best practices adherence
activities:
- Analyze code structure
- Check for security issues
- Review performance patterns
extensions:
- type: builtin
name: developer
display_name: Developer
timeout: 300
bundled: true
parameters:
- key: focus_area
input_type: string
requirement: optional
description: "Specific area to focus on (security, performance, readability, etc.)"
default: "general"
prompt: |
Please review the following code focusing on {{focus_area}} aspects.
Provide specific, actionable feedback with examples.
```
**Place your recipe file where Goose can find it**
- Set [`GOOSE_RECIPE_PATH`](/docs/guides/recipes/recipe-reference#recipe-location) environment variable to your recipe directory
- Or place it in your current working directory
**Goose Prompt**
```
Use the "code-reviewer" recipe to analyze the authentication feature I implemented
```
**Goose Output**
```
I'll use your code-reviewer recipe to create a specialized subagent for this analysis.
🤖 Subagent created using code-reviewer recipe
💭 Analyzing authentication function for security issues...
🔧 Scanning code structure and patterns...
⚠️ Security vulnerabilities detected!
## Code Review Results
### Critical Issues Found:
1. **SQL Injection Vulnerability**: Direct string interpolation in SQL query
2. **Missing Password Hashing**: Plain text password comparison
### Recommendations:
- Use parameterized queries or ORM
- Implement proper password hashing (bcrypt, scrypt)
- Add input validation and sanitization
```
## External Subagents
External subagents let you bring in AI agents from other providers and platforms, enabling Goose to coordinate and integrate your workflow with the broader ecosystem. In the below example, we use Codex as a subagent by running it as an MCP server:
**[Goose Configuration File](/docs/guides/config-file)** (`.~/.config/goose/config.yaml `):
```yaml
subagent:
args:
- mcp
bundled: true
cmd: codex
description: OpenAI Codex CLI Sub-agent
enabled: true
env_keys:
- OPENAI_API_KEY
envs: {}
name: subagent
timeout: 300
type: stdio
```
**External Tool Configuration** (`~/.codex/config.toml`):
```toml
# Use fast model for quick responses
# model = "codex-mini-latest"
disable_response_storage = true
# Never prompt for approval - auto-execute
approval_policy = "never"
[sandbox]
mode = "workspace-write"
```
**Goose Prompt:**
```
"Use the codex subagent to analyze my codebase structure and identify the main components"
```
**Goose Output:**
```md
Based on my analysis of your codebase, here are the main components:
1. **Core Agent System** (`crates/goose/src/agents/`)
- Agent orchestration and session management
- Tool execution framework
- Extension system integration
2. **CLI Interface** (`crates/goose-cli/`)
- Command-line interface and session handling
- Configuration management
3. **Server Components** (`crates/goose-server/`)
- HTTP API endpoints
- WebSocket communication for real-time interaction
4. **Desktop UI** (`ui/desktop/`)
- Electron-based desktop application
- TypeScript frontend with React components
The architecture follows a modular design with clear separation between the core agent logic, interfaces, and UI components.
```
## Suggested Use Cases
**Independent Operations**
- Creating multiple files with similar structure
- Basic data processing tasks
- File transformations and generations
**Context Preservation**
- Complex analysis that generates lots of tool output
- Specialized tasks better handled by dedicated agents
- Keeping main conversation focused on high-level decisions
**Process Isolation**
- Tasks that might fail without affecting main workflow
- Operations requiring different configurations
- Experimental or exploratory work
## Lifecycle and Cleanup
Subagents are temporary instances that exist only for task execution. After the task is completed, no manual intervention is needed for cleanup.
## Configuration
Subagents are automatically have the following pre-configured settings, but you can override any defaults using natural language in your prompts.
### Default Settings
| Parameter | Default | Source |
|-----------|---------|--------|
| **Max Turns** | 10 | Built-in default |
| **Timeout** | 5 minutes | Built-in default |
### Customizing Settings in Prompts
You can override any default by including the setting in your natural language request:
**Examples:**
```
"Use subagents to write a test and documentation, but make them timeout after 7 minutes"
```
```
""Use subagents to analyze code, limit each to 5 turns""
```
## Security Constraints
Subagents operate with restricted tool access to ensure safe execution and prevent interference with the main session.
### Allowed Operations
Subagents have access to these safe operations:
- **Extension discovery**: Search for available extensions to understand what tools are available
- **Resource access**: Read and list resources from enabled extensions for context
- **Extension tools**: Use tools from extensions specified in recipes or inherited from the parent session
### Restricted Operations
The following operations are blocked to ensure subagents remain focused on their assigned tasks without affecting the broader system state:
- **Subagent spawning**: Cannot create additional subagents to prevent infinite recursion
- **Extension management**: Cannot enable, disable, or modify extensions to avoid conflicts with the main session
- **Schedule management**: Cannot create, modify, or delete scheduled tasks to prevent interference with parent workflows
:::info
Subagents can browse extensions for suggestions but cannot enable them to avoid modifying the parent session.
:::
+1 -1
View File
@@ -1,6 +1,6 @@
---
title: Quick Goose Tips
sidebar_position: 6
sidebar_position: 30
sidebar_label: Quick Tips
description: Best practices for working with Goose
---
+1 -1
View File
@@ -1,5 +1,5 @@
---
sidebar_position: 5
sidebar_position: 20
title: Updating Goose
sidebar_label: Updating Goose
---
@@ -1,6 +1,6 @@
---
title: Providing Hints to Goose
sidebar_position: 7
sidebar_position: 40
sidebar_label: Using Goosehints
---
@@ -1,7 +1,7 @@
---
title: Prevent Goose from Accessing Files
sidebar_label: Using Gooseignore
sidebar_position: 14
sidebar_position: 80
---