Opus finding
ConfigAssistantPanel error path leaves user message in history with no assistant reply and no rollback
lowbughigh
- app/src/components/channels/mcp/ConfigAssistantPanel.tsx:41-78
On a failed configAssist call, the user message is already appended to messages and the input is cleared. The error is shown, but the user has no way to retry without re-typing — and on the next send the failed user message is still included in the history sent to the server, with no assistant turn in between. This violates the request/response shape that most LLM endpoints expect (alternating user/assistant) and can confuse the backend or the next call's history validation.
Recommendation
Either (a) roll back the user message on failure, or (b) keep it but allow retry that does not re-append the same user message. Optionally restore the input text on error so user can edit/retry.