ref(explorer): update hook to use useMutation

[aliu39]

Refactor useSeerExplorer to use useMutation for the 4 POST requests it can make. The previous style of api.requestPromise is deprecated and complicates on-success/error handling, while this is built into useMutation.

Temporarily removes the wasInterrupted state which showed a placeholder msg after interrupt requests. This state is hard to manage correctly and a low prio feature, especially since the current system for interrupts often fails. We can bring it back after reworking interrupts on the backend

[shruthilayaj]

Just a note, when we interrupt chat, could we remove this "thinking" block ("profiling your project" in this case)

[aliu39]

Just a note, when we interrupt chat, could we remove this "thinking" block ("profiling your project" in this case)

the clearOptimistic useEffect ("on partial load") should handle this once the interrupt succeeds. Unfortunately once we start processing the current system isn't able to interrupt before at least one assistant block is loaded

[cursor]

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 6ed04c8. Configure here.}

[cursor]

Stale interrupted prop on styled component now unused

Low Severity

StyledInputGroup still declares an interrupted prop in its type (<{interrupted?: boolean}>) and uses it to conditionally style placeholder text color (p.interrupted ? p.theme.tokens.content.warning : undefined), but this prop is no longer passed from any call site after removing wasJustInterrupted. This is dead styling logic that will never activate.

Additional Locations (1)

• static/app/views/seerExplorer/inputSection.tsx#L285-L286

 

^{Reviewed by Cursor Bugbot for commit 6ed04c8. Configure here.}