feat: Add troubleshooting for hermit error (#774)
This commit is contained in:
@@ -16,7 +16,7 @@ If Goose is heading in the wrong direction or gets stuck, you can interrupt it b
|
|||||||
---
|
---
|
||||||
|
|
||||||
### Stuck in a Loop or Unresponsive
|
### Stuck in a Loop or Unresponsive
|
||||||
In rare cases, Goose may enter a "death loop" or become unresponsive during a long session. This is often resolved by ending the current session, and starting a new session.
|
In rare cases, Goose may enter a "doom spiral" or become unresponsive during a long session. This is often resolved by ending the current session, and starting a new session.
|
||||||
|
|
||||||
1. Hold down `Ctrl + C` to cancel
|
1. Hold down `Ctrl + C` to cancel
|
||||||
2. Start a new session:
|
2. Start a new session:
|
||||||
@@ -39,6 +39,18 @@ Goose may encounter a `429 error` (rate limit exceeded) when interacting with LL
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
### Hermit Errors
|
||||||
|
|
||||||
|
If you see an issue installing an extension in the app that says "hermit:fatal", you may need to reset your hermit cache. We use
|
||||||
|
a copy of hermit to ensure npx and uvx are consistently available. If you have already used an older version of hermit, you may
|
||||||
|
need to cleanup the cache - on Mac this cache is at
|
||||||
|
|
||||||
|
```
|
||||||
|
sudo rm -rf ~/Library/Caches/hermit
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
### API Errors
|
### API Errors
|
||||||
|
|
||||||
Users may run into an error like the one below when there are issues with their LLM API tokens, such as running out of credits or incorrect configuration:
|
Users may run into an error like the one below when there are issues with their LLM API tokens, such as running out of credits or incorrect configuration:
|
||||||
|
|||||||
Reference in New Issue
Block a user