Repository navigation
fix(public-chat): a failed turn shows visitors a plain message, never the raw execution error (#3461) - #3478
Merged
Conversation
…never the operator's error (#3461) A public link's failed turn rendered the execution row's own `error` in the chat banner: the agent server's diagnosis ("Execution failed with no output (exit code 1): ...") followed by remediation addressed to the operator. The page is read by anonymous visitors. Two layers, because the page was only the last hop: - `GET /api/public/executions/{token}/{id}/status` is unauthenticated and returned `execution.error` verbatim for a `failed` row. It now answers the fixed line the synchronous public path already answers; the detail stays on the row for the operator. A cancel reason (#679) and a skill gate's notice (trinity#3274) are written for the visitor and still pass through. - `PublicChat.vue` no longer renders the status route's `error` for a failed turn at all. It shows one plain line and puts the visitor's message back in the input, so sending again is the retry. Tests, each red with its fix reverted and green with it restored: - src/frontend/tests/unit/publicChatFailureMessage.spec.js (mounted; 4/4 red under mutation, incl. "never renders the execution row's own error text") - tests/unit/test_3461_public_status_failure_text.py (2 red under mutation; the cancel and gate pass-through cases stay green) - tests/unit/test_679_public_poll_cancel.py: the `failed` case pinned the raw string and now pins the fixed line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
GET /api/public/executions/{token}/{id}/statusreturnedexecution.errorverbatim for a failed row. It now answers the fixed line the synchronous public path already uses; the detail stays on the row for the operator.test_679_public_poll_cancel.pypinned the raw string for failed rows and now pins the fixed line.PublicChat.vueshows a plain failure message and restores the visitor's message into the input for a retry; it never renders the status route'serrorfor a failed row.Part of the UI sweep epic #3471.
Related Issue
Fixes #3461
Journey Impact
Journey Impact: none: bug fix to existing behaviour found by the UI sweep; no journey promise is added or changed
Type of Change
Testing
Mutation:
publicChatFailureMessage.spec.js— 4 red with the view change reverted.tests/unit/test_3461_public_status_failure_text.py— 2 red with the route change reverted (plus the updated #679 case). Restored byte-identical.UI verification: on an isolated stack built from this change with a seeded failed execution whose stored error carries an exit code and operator remediation: the real
/statusresponse haserror: "Failed to process your request. Please try again.", the page shows the plain banner, restores the message into the input, and none of the raw strings appear in the DOM or console; checked at 1440 and 768, light and dark. The submit response was simulated in the browser because the seeded agent has no container; polling, status and rendering were real.Checklist
🤖 Generated with Claude Code