Description: While working on updating code in the canvas, I observed a difference in response behavior depending on whether the canvas was open or closed.
Issue Encountered:
Before making any updates, I intended to discuss adding new utility functions to my code. While the canvas was open, the assistant directly proceeded to edit the code in the open canvas editor instead of discussing the changes.
When I closed the canvas and asked the same question, the response was more conversational and aligned with my intention to discuss the approach without immediate edits.
Impact:
The assistant seems to prioritize direct edits to the code when the canvas is open instead of following the intended flow of conversation. This inconsistency affects the experience, leading to unintended edits when the user is not ready.
Suggested Improvement:
- Improve consistency between responses when the canvas is open vs closed, especially when discussing potential changes or planning next steps.
- Ensure the assistant can differentiate between when a user wants to discuss an idea versus making direct changes, regardless of the canvas state.