Feature request for product/service
Describe the request
Cursor currently overloads the word “Agent” in two different places: the left sidebar Agent list (task/history) and the chat mode selector labeled Agent (alongside Ask / Plan / Debug). This naming collision makes the mental model unclear and makes New Agent vs + New Chat feel redundant or ambiguous.
Proposal
Rename or reframe the left sidebar concept as a Session (or explicitly label it as such), representing where you are working on a task over time (history, plan review, file edits), distinct from a single chat thread.
Inside one Session, support multiple chat threads in parallel that share the same workspace/project context, while still enforcing context/token budgets and making it obvious what is shared vs isolated.
Treat the dropdown mode (Ask / Agent / Plan / Debug) as an interaction style within the active Session/thread, not as a second, competing definition of “Agent.” The UI and docs should make the hierarchy explicit: Session → thread/chat → mode.
This would reduce confusion between navigation (sidebar), conversation surface (+), and behavior (mode), and better match how users think about long-running work versus quick questions.