Often in the middle of a chat session with an agent, the agent is suddenly unable to see the terminal results. This either results in the agent incorrectly thinking they have fixed the problem I prompted them to solve, or it gets stuck in a loop trying more and more irrelevant things after already having solved the problem.
Steps to Reproduce
I have not found a consistent way to reproduce it, but it seems to eventually infect any chat session eventually
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Sometimes if I reload the window or start a new chat session, it is able to be fixed. So it seems to only affect existing chat sessions after enough terminal commands, but sometimes it can happen even within the first user prompt.
test session starts...
.
. # full pytest output here
.
1 failed, 3 passed, 18 warnings in 0.33s
Agent thinks: The test command seems to be running but not producing any output. Let me try a simpler approach to see if the tests are working.
This is really the only consistent pain point I’ve had using Cursor, but it’s been happening since forever and it would be really great if this issue could finally be solved.
Maybe I’m not using this correctly, but I would expect that refering a terminal would fetch the content of that terminal and make it available to the agent. This is not working though. Writing “Fix lint errors in @terminal” does not make agent aware of the content of that terminal window.
Steps to Reproduce
Try to reference the terminal for fixing bugs.
Expected Behavior
The agent should be aware of the content of the terminal.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
I’ve actually been experiencing this issue for quite some time, but I thought it might fix itself over time — unfortunately, it hasn’t.
Currently, I’m on version 1.6.45, and the problem still exists. I remember also noticing the same issue in v1.7, but since that release was unstable, I rolled back to the older version.
The issue: when we tag a message in the chat as terminal, it doesn’t recognize or process it.
Current Cursor Version (Menu → About Cursor → Copy)
Also the copy and paste feature in the terminal does not work. Ctrl+c stops the terminal.
cursor 1.6.45 cursor 1.6.45
The issue also occurs in the current conversation. I started a new conversation and added the terminal — it detected the terminal. But the feature to select an output in the terminal and copy it with Ctrl+C still doesn’t work.
I ran some commands in a terminal window, and then asked the Agent if it could see the output of said commands, and it told me that it couldn’t, that it didn’t have visibility (check screenshot).
This problem came since I updated Cursor to the latest version (1.5.11). In the older version that I had prior, the Agent was able to visualize the terminal without issues.
Steps to Reproduce
Open a terminal window.
Run a command in it.
Ask the Agent if it can see it by referencing it with “@”.
Agent says that it can’t.
Expected Behavior
…same as above…
4) Agent says that it can see the output.
Thanks for the extra info. Is this happening in a new chat, or has your chat been around for a while? Could you also share the request ID? To do that, you’ll need to turn off Privacy Mode.
The @Terminal tag works and I can select the correct console terminal from the list, but the content of the terminal is not attached to the chat.
When I ask the following:
Examing the console log here: @bash
I get the following:
The user wants me to examine console log for the application. I need to look for log files or run the application to see what's being logged to the console. Let me first check what log files might exist and also look at the application code to understand what logging is happening.
Let me start by searching for log files and understanding the logging setup in the application.
It has no context at all.
I know there is a workaround, but when will this in-chat feature get fixed?
Steps to Reproduce
Type @Terminal and select a terminal output to attach to chat.
Chat will have no context
Expected Behavior
Chat can read and analyze the log output
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
If I try to attach a currently running terminal to a new chat (including but not limited to sandbox terminals spawned in an earlier conversation), it doesn’t work. If I click the “@” and type “term”, all I get is the option “Add new terminal”.
If I type “@terminal” I can pick any of them, but it doesn’t actually add the terminal to the chat, just a reference that doesn’t hold any information.
This is pretty annoying because I don’t want to have to restart my frontend and backend each time I switch between conversations.
I use WSL.
Steps to Reproduce
first start a terminal
then start a new chat
terminal cannot be added to chat
Expected Behavior
I can type “@term”, pick one, and that terminal will get added to the chat context.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
