tkmind/tkmind_go
1
0
Fork 0
Code Issues Pull Requests Actions 4 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/troubleshooting/known-issues.md
-17
View File
@@ -114,23 +114,6 @@ For detailed steps on updating your LLM provider, refer to the [Installation][in
If you encounter errors when configuring GitHub Copilot as your provider, try these workarounds for common scenarios.
#### OAuth Error with Lead/Worker Models
If the [lead/worker model](/docs/tutorials/lead-worker) feature is configured in your environment, you might see the following error during GitHub Copilot setup. This feature conflicts with the OAuth flow to connect to the provider.
```
Failed to authenticate: Execution error: OAuth configuration not supported by this provider
```
To resolve:
1. Temporarily comment out or remove lead/worker model variables from the main config file (`~/.config/goose/config.yaml`):
```yaml
# GOOSE_LEAD_MODEL: your-model
# GOOSE_WORKER_MODEL: your-model
```
2. Run `goose configure` again to set up GitHub Copilot
3. Complete the OAuth authentication flow
4. Re-enable your lead/worker model settings as needed
#### Container and Keyring Issues
goose tries to use the system keyring (typically via Secret Service over DBus) to securely store your GitHub Copilot token. In containerized or headless environments, DBus and/or a desktop keyring service may not be available (and some setups fail with X11-based DBus autolaunch errors), so keyring access can fail.