feat: display browser runtime errors in the terminal #6251
Merged
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.

Summary
When building web applications with coding agents, we need to provide the LLM with enough context. One current limitation is that the agent cannot observe runtime errors occurring in the browser.
This PR addresses that by forwarding browser runtime errors to the socket server via WebSocket and logging them in the terminal, enabling the agent to access richer context for analysis and decision-making.
TODO
unhandledrejectioneventsRelated links
Checklist