All-Hands-AI
[Frontend] Short info to the user when there's an error
What problem or use case are you trying to solve? There are system errors that backend encounters, and the user should know the system isn't working right or they can change something. The easiest example is authentication errors, when I pick a non-existent model or have no access to it or my settings are otherwise wrong.
Describe the UX of the solution you'd like A system status field, maybe to the left of the Settings wheel, where we can display 'Authentication unsuccessful, please check settings' or some other clue about what went wrong. On backend, we can send some specific messages.
Do you have thoughts on the technical implementation? On backend we can try to use the task stop/reset feature on at least some exceptions.
Describe alternatives you've considered Maybe the field currently displaying info about the task (task has stopped, etc) could be used for this? I imagine we will also say the task is stopped though, so it seems like we need some other place for the reasons we can inform about. It doesn't have to be large (at all).
Additional context Auth is the easiest example, but maybe not the best: there are other suggestions on it discussed in other issues, like some sort of ping before starting the actual task, I'm not sure what that would imply, but I think there can be errors that we cannot know before they happen, like failing to condense despite best efforts and stopping on context window exceeded.
Related:
- https://github.com/OpenDevin/OpenDevin/pull/1445
- https://github.com/OpenDevin/OpenDevin/pull/1296
IMO we should reuse the bottom-center status indicator (currently just says if the agent is running or not)
@enyst there is a status now in the bottom middle of OpenDevin that shows high level status and I've seen some errors there. Is this what you were looking for?
I'm reopening this, because lately there have been multiple requests for important messages to be in a more accessible or visible way than in the logs, specially with docker app. Users request that relevant errors are more readily available or visible somehow. And we are listening, but we have started to make some changes to the UI adding some system / error messages in the chat box instead, since that's the ready place. Frankly, I think that doesn't look great, exceptions and raw code in-between natural language chat with the agent. Maybe there is a better way?
Perhaps we do need an actual "system status" after all, where the user can see the most important stuff (like quota exceeded, auth errors, budget exceeded).
Great idea! Maybe next to the settings cog wheel a "Notifications" indicator that on click opens pop-out sidebar from the right that shows those collected messages, with a clear list button? Everywhere where "toast.error" occurs, should also use that.
Going to use this as a catch all for better errors to the users going forward since you have some eyes on it.
https://github.com/OpenDevin/OpenDevin/pull/2657#issuecomment-2226781143
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}