Hi, thanks for reporting an issue with Cursor.
Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.
If you have done so, please check this box.
on
Describe the Bug
You can’t prompt using just lines from the terminal.
Attempting to continue a Composer conversation by pasting in lines from terminal triggers the (slightly frustrating) behaviour where it adds it above the discussion, you can’t paste it inline as part of your prompt (unless there’s a way to turn that off that I’ve missed). The issue is that if you don’t supply an additional text prompt, you’ll get no LLM response when you submit. Instead the display changes to show a collapsed ‘dots’ view of diffs, and it seems like everything has stalled, when in fact you’ll just get nothing back.
Steps to Reproduce
- Do something that generates terminal output
- Copy a couple of lines from it
- Paste them into Composer intending to submit them as a prompt
- Submit
Expected Behavior
If the only thing you need to send as a prompt is the terminal output, there should really be a way to do that and get a response
Operating System
Windows 10/11
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.44.5
VSCode Version: 1.93.1
Commit: 1d610252e6812bf33245763f0742a534fd0f1d90
Date: 2024-12-20T00:02:28.554Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Additional Information
I’ve been working around it by pasting into a text editor, then re-copying, and then you can paste as plain text. BUT you have to make it at least one character different, otherwise it seems it’ll get recognised as the same thing and taken out of the text prompt and “attached” again.
Does this stop you from using Cursor
No - Cursor works, but with this issue