Receipt · eba8958d-0
ConfigAssistantPanel error path leaves user message in history with no assistant reply and no rollback
buglow
repo df3ede3f·PR #2·reviewed 1 week ago
The finding
- 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.
Fix
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.
Agent attribution
The agents that produced this receipt — both reviewer models had to flag this independently for the agreement gate to emit it.
anthropic
gpt-5
66.5s · error
openai
claude-opus-4-7
149.2s · error
Total
wall-clock review time · est. inference cost
149.2s · $0.40
Sweeper
closed at SHA
still open
internal review id · eba8958d
Third-party witnesses
Everything below lives on GitHub's event log, not ours. Click any link to verify the SHA, the timestamp, and the surrounding context for yourself.
Original review comment
https://github.com/AntFleet/agent-openhuman-bench/pull/2#issuecomment-4494700328