Wendy Tang
Wendy Tang
+1 looking forward to this feature
Related #1624 - error handling: tool call errors shouldn't take down the entire session, we should provide a way to recover
Hi @gzuuus, why would you need to disable them? These tools are built in to assist with extensions, so might you have triggered them by asking about extensions?
It looks like goose had a problem creating the log file - try creating it if it didn't create ``` mkdir -p ~/.config/goose/logs && chmod 755 ~/.config/goose/logs ``` Not aware...
If you run into this issue, check the ownership of your ~/.local/* folders ``` ls -lad ~/.local ~/.local/share ~/.local/share/goose ~/.local/state ~/.config ``` If any of the folders are not owned...
@Dan-Wuensch let us know if that works for you ^
thanks for letting us know! We're unlikely going to address this because goose outputs to stdout in a pretty simple way, and I don't see a straightforward way to re-render...
Also you could start with using a bigger terminal window
hi @bertlebee, nice contribution! it looks close - added a comment.
i haven't run into the rate limit before, but does #1820 help fix what you were experiencing? i added a 300 char limit to your change, wondering if you could...