Where does the bug appear (feature/product)? Somewhere else… Describe the Bug Cursor SDK Issue: agent.send() does not retain conversation context across runs Summary When using @cursor/sdk with local agents, calling agent.send() multiple times on the same agent does not retain conversation context …

This is a confirmed bug — each send() on a local agent starts a fresh run without loading prior conversation state. Cloud agents handle this server-side and work correctly. I’m merging this into an existing thread where the same issue was reported and acknowledged: [SDK] Local agents do not retai…

Hey @codjust , We’ve made changes in this area since you posted — local agents retaining conversation context across agent.send() calls now works on the latest version of the SDK. Could you give it another try? Quick check: Update to the latest @cursor/sdk Run your minimal two-turn repro script (…

Cursor SDK Issue: `agent.send()` does not retain conversation context across runs

Support Bug Reports

Topic		Replies	Views
[SDK] Local agents do not retain conversation context between agent.send() calls` Bug Reports context , cloud-agents , cursor-sdk	9	297	August 22, 2026
Idle local agent gRPC connection returns `ERROR_NOT_LOGGED_IN` (AuthenticationError) instead of NetworkError after ~15 minutes Bug Reports cursor-sdk	3	113	August 27, 2026
Agent.send().wait() returns bare status: "error" while ConnectRPC [unauthenticated] leaks as unhandledRejection Bug Reports cloud-agents , long-running-agents , cursor-sdk	4	144	July 8, 2026
Cursor SDK agent.send() does not retain conversation context across runs Bug Reports	1	103	May 5, 2026
Cursor-agent CLI: TUI fails with `NGHTTP2_ENHANCE_YOUR_CALM` once skill payload exceeds ~11 MB; no scoping option Bug Reports skills , crashes , cli	4	198	August 27, 2026

Cursor SDK Issue: `agent.send()` does not retain conversation context across runs

Related topics