Adding existing terminals to new chat doesn't work

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

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 :cry:

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)

Version: 1.7.39 (user setup)
VSCode Version: 1.99.3
Commit: a9c77ceae65b77ff772d6adfe05f24d8ebcb2790
Date: 2025-10-08T00:33:20.352Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 posts were merged into an existing topic: Agent loses terminal output