Agent doesn't reuse the existing conversation when being @ on GitHub

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I really enjoy to @cursor on my github issues to start a conversation about the issue. However, after Cursor bot has responded to my request, if I @cursor again to give it follow up instructions, it will create a new background Agent to treat my follow up question.

Steps to Reproduce

@cursor once on github, then @ it again and watch it create a separate background agent for the second request

Expected Behavior

I’d like the agent to consider my comment as a follow up prompt, and re-use the existing conversation with the agent that was created for the first @.

My main motivation is that, when working on multiple issues at once, the list of agents quickly becomes an absolute mess and I can’t remember which agent has been “superseeded” by another or not.

Operating System

Windows 10/11
MacOS
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11 (Universal)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

gpt5 / gpt5-high

Does this stop you from using Cursor

No - Cursor works, but with this issue

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.