-
I agree, retry makes sense, but how "regenerate" is supposed to be working? Is it the same as "retry"?
As for the partial responses, I encountered this problem myself. Sometimes Grok sends only partial responses. Even if I resent the same query, I get the same partial response. I am afraid this might be a problem on the Grok side. But, in any case I will keep an eye on it.
-
For the regenerate, sometimes grok can give a response which is incorrect. Generally I find that on the Grok Web UI if I tell it to try again it will give a better response. This is especially useful if there is the ability to edit the previous message to better phrase the request. Perhaps this would be the same button as a retry on a timeout or other API error.
-
Hm, ok, so you suggest, maybe that the retry function would copy your last query to grok, allow you to edit it, maybe change temperature (or not edit) and send it again? Or maybe you are thinking about something else?
I can also look at the API if there is a way to have something similar to Grok web ui called: "Think harder".
| Type |
Improvement
|
| Priority |
Normal
|
| Assignees |
Not assigned
|
A retry button when grok has an API timeout would be very nice.
EDIT: With this, a regenerate response button is also needed for when grok provides a partial answer.