Feature request for product/service
Cursor CLI
Describe the request
Feature Request: Ability to Resume Headless Cursor-Agent Sessions
Today, interactive cursor-agent CLI sessions can be resumed because their state is persisted locally on the host. However, when running the agent in headless mode (e.g., via automation scripts or background processes), the session context is not stored in a way that allows resuming or reattaching later.
For enterprise and DevOps scenarios, it would be extremely valuable if headless cursor-agent executions could share the same session persistence model as interactive sessions — ideally with a clear option to configure:
-
Named session identifiers for headless runs
-
Persistent storage location parameters
-
Ability to reattach or continue a previous headless session
This would enable long-running, automated workflows while maintaining full context over time, improving reliability and reducing repetitive initialization costs.
Thanks for considering this enhancement — it would significantly boost Cursor’s suitability for scalable, automated development environments.
If you’d like, I can also:
Add concrete examples / use cases
Propose CLI parameter syntax
Reference best practices from comparable agent models (e.g., MCP server usage)
Operating System (if it applies)
Linux