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

chore: remove autopilot experimental feature (#5781)

Browse Source
This commit is contained in:
Michael Neale
2025-11-19 11:49:05 +11:00
committed by GitHub
parent 5ba636f45f
commit f8bb866264
14 changed files with 6 additions and 1751 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/tutorials/lead-worker.md
+1 -5
View File
@@ -25,10 +25,6 @@ The lead/worker model is a smart hand-off system. The "lead" model (think: GPT-4
If things go sideways (e.g. the worker model gets confused or keeps making mistakes), Goose notices and automatically pulls the lead model back in to recover. Once things are back on track, the worker takes over again.
:::tip Consider AutoPilot for Advanced Model Switching
[AutoPilot](/docs/guides/multi-model/autopilot) supports turn-based switching and also offers intelligent context-aware switching between multiple models.
:::
## Turn-Based System
A **turn** is one full interaction - your prompt and the model's response. Goose switches models based on turns:
@@ -127,4 +123,4 @@ export GOOSE_LEAD_MODEL="o1-preview" # the lead model used automatically
export GOOSE_PLANNER_MODEL="gpt-4o" # the model used when you explicitly call /plan
```
Use **planning mode** when you want a dedicated reasoning model to generate comprehensive strategies that you can review and approve before execution. Use the **lead/worker model** for iterative development work where you want smart automation without interruption - like implementing features, debugging issues, or exploratory coding. Your workflow can combine both: use `/plan` to strategize major decisions, then let the lead/worker models handle the tactical implementation with automatic optimization.
Use **planning mode** when you want a dedicated reasoning model to generate comprehensive strategies that you can review and approve before execution. Use the **lead/worker model** for iterative development work where you want smart automation without interruption - like implementing features, debugging issues, or exploratory coding. Your workflow can combine both: use `/plan` to strategize major decisions, then let the lead/worker models handle the tactical implementation with automatic optimization.