docs: remove subagents from experimental (#4907)

documentation/docs/experimental/index.md

@@ -19,11 +19,6 @@ The list of experimental features may change as Goose development progresses. So
 <div className={styles.categorySection}>
   <h2 className={styles.categoryTitle}>🧪 Experimental Features</h2>
   <div className={styles.cardGrid}>
-      <Card 
-      title="Subagents"
-      description="Independent instances that execute tasks while keeping your main conversation clean and focused. Run tasks sequentially or in parallel with process isolation and context preservation."
-      link="/docs/experimental/subagents"
-    />
     <Card 
       title="Ollama Tool Shim"
       description="Enable tool calling capabilities for language models that don't natively support tool calling (like DeepSeek) using an experimental local interpreter model setup."
@@ -44,6 +39,11 @@ The list of experimental features may change as Goose development progresses. So
       description="Intelligent, context-aware switching between models based on conversation content, complexity, and tool usage patterns."
       link="/docs/guides/multi-model/autopilot"
     />
+    <Card 
+      title="Using goose in ACP Clients"
+      description="Interact with goose natively in ACP-compatible clients like Zed."
+      link="/docs/guides/acp-clients"
+    />
   </div>
 </div>
 

documentation/docs/guides/acp-clients.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 25
+sidebar_position: 105
 title: Using Goose in ACP Clients
 sidebar_label: Goose in ACP Clients
 ---

documentation/docs/guides/allowlist.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 19
+sidebar_position: 90
 title: Goose Extension Allowlist
 sidebar_label: Extension Allowlist
 ---

documentation/docs/guides/cli-providers.md

@@ -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

documentation/docs/guides/config-file.md

@@ -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.
 

documentation/docs/guides/enhanced-code-editing.md

@@ -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.

documentation/docs/guides/environment-variables.md

@@ -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**
 

documentation/docs/guides/file-management.md

@@ -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
 ---

documentation/docs/guides/goose-cli-commands.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 7
+sidebar_position: 35
 title: CLI Commands
 sidebar_label: CLI Commands
 toc_max_heading_level: 4

documentation/docs/guides/goose-permissions.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 25
 title: Goose Permission Modes
 sidebar_label: Goose Permissions
 ---

documentation/docs/guides/handling-llm-rate-limits-with-goose.md

@@ -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';

documentation/docs/guides/interactive-chat/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "Rich Interactive Chat",
-  "position": 8,
+  "position": 55,
   "link": {
     "type": "doc",
     "id": "guides/interactive-chat/index"

documentation/docs/guides/logs.md

@@ -1,7 +1,7 @@
 ---
 title: Goose Logging System
 sidebar_label: Logging System
-sidebar_position: 9
+sidebar_position: 65
 ---
 
 

documentation/docs/guides/managing-projects.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 15
 title: Managing Projects
 sidebar_label: Managing Projects
 ---

documentation/docs/guides/managing-tools/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "Managing Tools",
-  "position": 4,
+  "position": 15,
   "link": {
     "type": "doc",
     "id": "guides/managing-tools/index"

documentation/docs/guides/multi-model/_category_.json

@@ -1,5 +1,5 @@
 {
   "label": "Multi-Model Config",
-  "position": 20,
+  "position": 100,
   "description": "Configure multiple models and providers for model-switching strategies."
 }

documentation/docs/guides/recipes/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "Recipes",
-  "position": 2,
+  "position": 5,
   "link": {
     "type": "doc",
     "id": "guides/recipes/index"

documentation/docs/guides/running-tasks.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 13
+sidebar_position: 75
 title: Running Tasks
 sidebar_label: Run Tasks
 ---

documentation/docs/guides/subagents.md

@@ -1,15 +1,11 @@
 ---
 title: Subagents
-sidebar_position: 1
+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.
 
-:::warning
-Subagents are an experimental feature in active development. Behavior and configuration may change in future releases.
-:::
-
 ## 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:
@@ -30,20 +26,6 @@ You can run multiple subagents sequentially or in parallel.
 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.
 :::
 
-
-## Prerequisites
-To use subagents, you need to enable alpha features first. You can do this by setting an [environment variable](/docs/guides/environment-variables#experimental-features) or adding it to your [config file](/docs/guides/config-file#experimental-features):
-
-**Environment Variable:**
-```bash
-export ALPHA_FEATURES=true
-```
-
-**Config File** (`~/.config/goose/config.yaml`):
-```yaml
-ALPHA_FEATURES: true
-```
-
 ## 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:

documentation/docs/guides/tips.md

@@ -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
 ---

documentation/docs/guides/updating-goose.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 20
 title: Updating Goose
 sidebar_label: Updating Goose
 ---

documentation/docs/guides/using-goosehints.md

@@ -1,6 +1,6 @@
 ---
 title: Providing Hints to Goose
-sidebar_position: 7
+sidebar_position: 40
 sidebar_label: Using Goosehints
 ---
 

documentation/docs/guides/using-gooseignore.md

@@ -1,7 +1,7 @@
 ---
 title: Prevent Goose from Accessing Files
 sidebar_label: Using Gooseignore
-sidebar_position: 14
+sidebar_position: 80
 ---
 
 

documentation/docs/tutorials/plan-feature-devcontainer-setup.md

@@ -452,6 +452,6 @@ The key is treating Goose as a planning partner, not just a code generator. Give
 - Try this approach with your own complex setup challenges
 - Experiment with different types of planning prompts
 - Share your planning successes with the [Goose community](https://discord.gg/block-opensource)
-- Explore how planning integrates with [Lead/Worker mode](/docs/tutorials/lead-worker) or [Subagents](/docs/experimental/subagents) for even more sophisticated workflows
+- Explore how planning integrates with [Lead/Worker mode](/docs/tutorials/lead-worker) or [Subagents](/docs/guides/subagents) for even more sophisticated workflows
 
 Remember, the goal is to get the right approach, in the right order, with the right safeguards. That's what makes the difference between a quick fix and a robust, maintainable solution.