tool call results in JSON unmarshal error

[mgood]

Description

Over the last few days, I've had this come up several times where after tool calls I get:

ERROR Provider Error
json: cannot unmarshal string into Go value of type apierror.Error

This seems like there's some other underlying error, but it's getting masked by the unmarshalling where there's a field for the error, but apierror.Error doesn't implement Unmarshaller.
In this case it happened after an LSP Diagnostics tool call, but I'm not sure if the others were the same.
I'll try to get more info if it happens again.

Version

0.95.0

Environment

Mac, Ghostty, nono sandboxing

[mgood]

Oh I see now #3856 has a similar issue, but I got thrown off by the subject being about the api key.

After I finished filing this, I checked another running crush session and saw that a Bash call there had also resulted in this error.

I'm not sure if it's a regression with one of the recent version updates, or I've also been using more parallel crush sessions lately.

[vladp]

I am also running into this error, I do not think (at least in my case) it is tool related. I just had setup a new model and getting this error, I am not sure what exactly wrong with my setup, as the error is masked
v0.95, running on NetBSD 11 x86_64