tkmind/tkmind_go
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

docs: remove unsupported lead/worker docs and scripts (#8471)

Browse Source 
Signed-off-by: Mark Shaggy <keramshag@gmail.com>
Signed-off-by: Angie Jones <jones.angie@gmail.com>
Co-authored-by: Angie Jones <jones.angie@gmail.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
markshaggy
2026-04-11 00:59:27 +02:00
committed by GitHub
parent 00a4d056fb
commit 0e743112ea
18 changed files with 50 additions and 262 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/guides/cli-providers.md
+8 -8
View File
@@ -37,7 +37,7 @@ CLI providers are useful if you:
#### Workflow Integration
- **Recipe compatibility**: Use CLI providers in automated goose recipes
- **Scheduling support**: Include in scheduled tasks and workflows
- **Hybrid configurations**: Combine with LLM providers using lead/worker patterns
- **Hybrid configurations**: Combine with planning mode and model-specific workflows
#### Interface Consistency
- **Unified commands**: Use the same `goose session` interface across all providers
@@ -260,16 +260,16 @@ Once configured, you can start a goose session using these providers just like a
goose session
```
### Combining with Other Models
### Combining with Planner Models
CLI providers work well in combination with other models using goose's [lead/worker pattern](/docs/tutorials/lead-worker):
CLI providers also work well with planning mode when you want one model for strategy and another for execution:
```bash
# Use Claude Code as lead model, GPT-4o as worker
export GOOSE_LEAD_PROVIDER=claude-code
export GOOSE_PROVIDER=openai
export GOOSE_MODEL=gpt-4o
export GOOSE_LEAD_MODEL=default
# Use Claude Code for execution, OpenAI for planning
export GOOSE_PROVIDER=claude-code
export GOOSE_MODEL=default
export GOOSE_PLANNER_PROVIDER=openai
export GOOSE_PLANNER_MODEL=gpt-4o
goose session
```
documentation/docs/guides/config-files.md
-2
View File
@@ -37,8 +37,6 @@ The following settings can be configured at the root level of your config.yaml f
| `GOOSE_MAX_TOKENS` | Maximum number of tokens for each model response (truncates longer responses) | Positive integer | Model-specific | No |
| `GOOSE_MODE` | [Tool execution behavior](/docs/guides/goose-permissions) | "auto", "approve", "chat", "smart_approve" | "auto" | No |
| `GOOSE_MAX_TURNS` | [Maximum number of turns](/docs/guides/sessions/smart-context-management#maximum-turns) allowed without user input | Integer (e.g., 10, 50, 100) | 1000 | No |
| `GOOSE_LEAD_PROVIDER` | Provider for lead model in [lead/worker mode](/docs/guides/environment-variables#leadworker-model-configuration) | Same as `GOOSE_PROVIDER` options | Falls back to `GOOSE_PROVIDER` | No |
| `GOOSE_LEAD_MODEL` | Lead model for lead/worker mode | Model name | None | No |
| `GOOSE_PLANNER_PROVIDER` | Provider for [planning mode](/docs/guides/creating-plans) | Same as `GOOSE_PROVIDER` options | Falls back to `GOOSE_PROVIDER` | No |
| `GOOSE_PLANNER_MODEL` | Model for planning mode | Model name | Falls back to `GOOSE_MODEL` | No |
| `GOOSE_TOOLSHIM` | Enable tool interpretation | true/false | false | No |
documentation/docs/guides/creating-plans.md
+1 -1
View File
@@ -35,7 +35,7 @@ The goose CLI plan mode uses two configuration values:
- `GOOSE_PLANNER_MODEL`: Which model to use for planning
:::tip Multi-Model Alternative to Plan Mode
goose also supports automatic model switching with [Lead/Worker mode](/docs/guides/environment-variables#leadworker-model-configuration), which provides turn-based switching between two models to help balance model capabilities with cost and speed.
You can combine planning mode with a different default execution model to balance cost, speed, and quality.
:::
:::tip Customize Plan Format
documentation/docs/guides/environment-variables.md
-40
View File
@@ -130,40 +130,6 @@ export GOOSE_PREDEFINED_MODELS='[
Custom context limits and request parameters are applied when the model is used. Custom context limits are displayed in goose CLI's [token usage indicator](/docs/guides/sessions/smart-context-management#token-usage).
### Lead/Worker Model Configuration
These variables configure a [lead/worker model pattern](/docs/tutorials/lead-worker) where a powerful lead model handles initial planning and complex reasoning, then switches to a faster/cheaper worker model for execution. The switch happens automatically based on your settings.
| Variable | Purpose | Values | Default |
|----------|---------|---------|---------|
| `GOOSE_LEAD_MODEL` | **Required to enable lead mode.** Name of the lead model | Model name (e.g., "gpt-4o", "claude-sonnet-4-20250514") | None |
| `GOOSE_LEAD_PROVIDER` | Provider for the lead model | [See available providers](/docs/getting-started/providers#available-providers) | Falls back to `GOOSE_PROVIDER` |
| `GOOSE_LEAD_TURNS` | Number of initial turns using the lead model before switching to the worker model | Integer | 3 |
| `GOOSE_LEAD_FAILURE_THRESHOLD` | Consecutive failures before falling back to the lead model | Integer | 2 |
| `GOOSE_LEAD_FALLBACK_TURNS` | Number of turns to use the lead model in fallback mode | Integer | 2 |
A _turn_ is one complete prompt-response interaction. Here's how it works with the default settings:
- Use the lead model for the first 3 turns
- Use the worker model starting on the 4th turn
- Fallback to the lead model if the worker model struggles for 2 consecutive turns
- Use the lead model for 2 turns and then switch back to the worker model
The lead model and worker model names are displayed at the start of the goose CLI session. If you don't export a `GOOSE_MODEL` for your session, the worker model defaults to the `GOOSE_MODEL` in your [configuration file](/docs/guides/config-files).
**Examples**
```bash
# Basic lead/worker setup
export GOOSE_LEAD_MODEL="o4"
# Advanced lead/worker configuration
export GOOSE_LEAD_MODEL="claude4-opus"
export GOOSE_LEAD_PROVIDER="anthropic"
export GOOSE_LEAD_TURNS=5
export GOOSE_LEAD_FAILURE_THRESHOLD=3
export GOOSE_LEAD_FALLBACK_TURNS=2
```
### Claude Thinking Configuration
These variables control Claude's reasoning behavior. Supported on Anthropic and Databricks providers.
@@ -350,8 +316,6 @@ These variables allow you to override the default context window size (token lim
|----------|---------|---------|---------|
| `GOOSE_CONTEXT_LIMIT` | Override context limit for the main model | Integer (number of tokens) | Model-specific default or 128,000 |
| `GOOSE_INPUT_LIMIT` | Override input prompt limit for ollama requests (maps to `num_ctx`) | Integer (number of tokens) | Falls back to `GOOSE_CONTEXT_LIMIT` or model default |
| `GOOSE_LEAD_CONTEXT_LIMIT` | Override context limit for the lead model in [lead/worker mode](/docs/tutorials/lead-worker) | Integer (number of tokens) | Falls back to `GOOSE_CONTEXT_LIMIT` or model default |
| `GOOSE_WORKER_CONTEXT_LIMIT` | Override context limit for the worker model in lead/worker mode | Integer (number of tokens) | Falls back to `GOOSE_CONTEXT_LIMIT` or model default |
| `GOOSE_PLANNER_CONTEXT_LIMIT` | Override context limit for the [planner model](/docs/guides/creating-plans) | Integer (number of tokens) | Falls back to `GOOSE_CONTEXT_LIMIT` or model default |
**Examples**
@@ -362,10 +326,6 @@ export GOOSE_CONTEXT_LIMIT=200000
# Override ollama input prompt limit
export GOOSE_INPUT_LIMIT=32000
# Set different context limits for lead/worker models
export GOOSE_LEAD_CONTEXT_LIMIT=500000 # Large context for planning
export GOOSE_WORKER_CONTEXT_LIMIT=128000 # Smaller context for execution
# Set context limit for planner
export GOOSE_PLANNER_CONTEXT_LIMIT=1000000
```
documentation/docs/guides/multi-model/index.mdx
+7 -14
View File
@@ -19,9 +19,9 @@ import VideoCarousel from '@site/src/components/VideoCarousel';
<h2 className={styles.categoryTitle}>📚 Documentation & Guides</h2>
<div className={styles.cardGrid}>
<Card
title="Lead/Worker Multi-Model Setup"
description="Automatic switching between models using a lead model for initial turns and a worker model for execution."
link="/docs/tutorials/lead-worker"
title="Planner + Execution Model Setup"
description="Use a dedicated planner model for strategic reasoning and a separate default model for execution."
link="/docs/guides/creating-plans"
/>
<Card
title="Creating Plans Before Working"
@@ -45,9 +45,9 @@ import VideoCarousel from '@site/src/components/VideoCarousel';
link="/blog/2025/06/16/multi-model-in-goose"
/>
<Card
title="LLM Tag Team: Who Plans, Who Executes?"
description="Learn how lead/worker model configuration creates an effective AI tag team, with one model for planning and another for execution."
link="/blog/2025/08/11/llm-tag-team-lead-worker-model"
title="The AI Skeptic's Guide to Context Windows"
description="Learn practical ways to manage context windows and token usage in long-running sessions."
link="/blog/2025/08/18/understanding-context-windows"
/>
</div>
</div>
@@ -62,15 +62,8 @@ import VideoCarousel from '@site/src/components/VideoCarousel';
type: 'iframe',
src: 'https://www.youtube.com/embed/ZyhUTsChFUw',
title: 'goose\'s Multi-Model Setup',
description: 'Learn about lead/worker mode, from configuration to best practices',
description: 'Learn practical multi-model workflows in goose',
duration: '5:01'
},
{
type: 'iframe',
src: 'https://www.youtube.com/embed/SJ6EZpyCKrk',
title: 'Livestream - LLM Tag Team: Who Plans, Who Executes?',
description: 'Using lead/worker mode to add features to the goose docs in real time',
duration: '9:36'
}
]}
/>
documentation/docs/guides/sessions/smart-context-management.md
+5 -8
View File
@@ -293,8 +293,6 @@ Context limits are automatically detected based on your model name, but goose pr
| Model | Description | Best For | Setting |
|-------|-------------|----------|---------|
| **Main** | Set context limit for the main model (also serves as fallback for other models) | LiteLLM proxies, custom models with non-standard names | `GOOSE_CONTEXT_LIMIT` |
| **Lead** | Set larger context for planning in [lead/worker mode](/docs/tutorials/lead-worker) | Complex planning tasks requiring more context | `GOOSE_LEAD_CONTEXT_LIMIT` |
| **Worker** | Set smaller context for execution in lead/worker mode | Cost optimization during execution phase | `GOOSE_WORKER_CONTEXT_LIMIT` |
| **Planner** | Set context for [planner models](/docs/guides/creating-plans) | Large planning tasks requiring extensive context | `GOOSE_PLANNER_CONTEXT_LIMIT` |
:::info
@@ -311,7 +309,7 @@ This feature is particularly useful with:
goose resolves context limits with the following precedence (highest to lowest):
1. Explicit context_limit in model configuration (if set programmatically)
2. Specific environment variable (e.g., `GOOSE_LEAD_CONTEXT_LIMIT`)
2. Specific environment variable (e.g., `GOOSE_PLANNER_CONTEXT_LIMIT`)
3. Global environment variable (`GOOSE_CONTEXT_LIMIT`)
4. Model-specific default based on name pattern matching
5. Global default (128,000 tokens)
@@ -348,13 +346,12 @@ export GOOSE_MODEL="my-custom-gpt4-proxy"
export GOOSE_CONTEXT_LIMIT=200000 # Override the 32k default
```
2. Lead/worker setup with different context limits
2. Planner setup with a different context limit
```bash
# Different context limits for planning vs execution
export GOOSE_LEAD_MODEL="claude-opus-custom"
export GOOSE_LEAD_CONTEXT_LIMIT=500000 # Large context for planning
export GOOSE_WORKER_CONTEXT_LIMIT=128000 # Smaller context for execution
# Set a larger context window for planning
export GOOSE_PLANNER_MODEL="claude-opus-custom"
export GOOSE_PLANNER_CONTEXT_LIMIT=500000
```
3. Planner with large context
documentation/docs/guides/tips.md
+2 -2
View File
@@ -57,8 +57,8 @@ goose Desktop lets you [customize the sidebar](/docs/guides/desktop-navigation)
### Keep goose updated
Regularly [update](/docs/guides/updating-goose) goose to benefit from the latest features, bug fixes, and performance improvements.
### Pair Two Models to Save Money
Use [lead/worker model](/docs/tutorials/lead-worker/) to have goose use a "lead" model for early planning before handing the task to a lower-cost "worker" model for execution.
### Use a Dedicated Planner Model
Use [planning mode](/docs/guides/creating-plans) with a dedicated planner model for complex reasoning, while keeping a faster default model for everyday execution.
### Make Recipes Safe to Re-run
Write [recipes](/docs/guides/recipes/session-recipes) that check your current state before acting, so they can be run multiple times without causing any errors or duplication.