Explains Rather than Implements #8472
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
I've noticed today on the preview build the agents keeps explaining what to do rather than doing it. That leaves me asking/telling it to implement the feature it just described. I feel that this is just doubling token usage since it sent it once to tell me about it, and will have to send it again to implement.
To reproduce
I'm trying to have it fix a bug.
ie:
When I drag and drop an item from a child node from within something like an object or list up to the root node, it duplicates it leaving the original where it started rather than moving/deleting it.
Previously I feel like these types of request were understood to be identified and fixed/implemented, but that no longer seems to be the case. I'm fine with clarifying questions or forks in the road, but it seems that's not the case. I had it tell me to copy and paste the content of the files one of the times today! 😆 Do I need to change my prompting to now always include "implement the change", "implement the change if there are no questions, otherwise ask for clarification" ?
Expected behavior
It should more often than not, be implementing rather than just telling me about a fix or telling me to update the source files.
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
15.6.1 (24G90)
Shell Version
zsh 5.9 (arm64-apple-darwin24.0)
Current Warp version
v0.2026.01.14.08.15.preview_03
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
Seems like something that started in the last day or few
Additional context
No response
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None