feat(explorer): stop polling on api error and show status code in empty state#114273
feat(explorer): stop polling on api error and show status code in empty state#114273
Conversation
github-actions
Bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b5de474. Configure here.
| ) => { | ||
| if (isError) { | ||
| return false; | ||
| } |
There was a problem hiding this comment.
Error stopping polling falsely triggers "done-thinking" indicator
Low Severity
When an API error occurs while the drawer is closed, isPolling transitions from true to false. The SeerExplorerContextProvider interprets any polling→not-polling transition (while the drawer is closed) as "done-thinking" and shows an accent dot indicator on the Seer button. This gives the user a false signal that the agent completed its work, when it actually errored out. Before this change, errors never stopped polling, so this path was never hit.
Reviewed by Cursor Bugbot for commit b5de474. Configure here.
There was a problem hiding this comment.
erroring out counts as having an update imo
…ty state (#114273) Right now we poll forever when there's an api error. Stop polling on error and show the status code if it's empty state. It'll be up to the users to trigger refetches (reload page or nav away from the chat and come back). Also disables new chat button when runId = null instead of empty state, so you can start a new chat from the error state <img width="703" height="636" alt="Screenshot 2026-04-29 at 7 32 11 PM" src="https://github.com/user-attachments/assets/ceec988b-592d-4211-92cb-24a74866e86d" /> <img width="644" height="366" alt="image" src="https://github.com/user-attachments/assets/72b97237-691c-4464-988e-ac834f4a1c32" />
2 participants
Right now we poll forever when there's an api error. Stop polling on error and show the status code if it's empty state. It'll be up to the users to trigger refetches (reload page or nav away from the chat and come back).
Also disables new chat button when runId = null instead of empty state, so you can start a new chat from the error state