feat: lead/worker model (#2719)

This commit is contained in:
Michael Neale
2025-06-05 13:55:32 +10:00
committed by GitHub
parent 6076c9b5dc
commit 2f8f8e5767
9 changed files with 1088 additions and 11 deletions
+25
View File
@@ -23,6 +23,31 @@ Whether you're prototyping an idea, refining existing code, or managing intricat
Designed for maximum flexibility, goose works with any LLM, seamlessly integrates with MCP servers, and is available as both a desktop app as well as CLI - making it the ultimate AI assistant for developers who want to move faster and focus on innovation.
## Multiple Model Configuration
goose supports using different models for different purposes to optimize performance and cost, which can work across model providers as well as models.
### Lead/Worker Model Pattern
Use a powerful model for initial planning and complex reasoning, then switch to a faster/cheaper model for execution, this happens automatically by goose:
```bash
# Required: Enable lead model mode
export GOOSE_LEAD_MODEL=modelY
# Optional: configure a provider for the lead model if not the default provider
export GOOSE_LEAD_PROVIDER=providerX # Defaults to main provider
```
### Planning Model Configuration
Use a specialized model for the `/plan` command in CLI mode, this is explicitly invoked when you want to plan (vs execute)
```bash
# Optional: Use different model for planning
export GOOSE_PLANNER_PROVIDER=openai
export GOOSE_PLANNER_MODEL=gpt-4
```
Both patterns help you balance model capabilities with cost and speed for optimal results, and switch between models and vendors as required.
# Quick Links
- [Quickstart](https://block.github.io/goose/docs/quickstart)