# Cursor Headless mode supports persistent processes

**URL:** <https://forum.cursor.com/t/cursor-headless-mode-supports-persistent-processes/150983>\
**Category:** Feature Requests\
**Tags:** cli, performance\
**Created:** [February 6, 2026, 1:06am UTC](https://forum.cursor.com/t/cursor-headless-mode-supports-persistent-processes/150983 "2026-02-06T01:06:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lyx](https://avatars.discourse-cdn.com/v4/letter/l/3d9bf3/32.png) [@lyx](https://forum.cursor.com/u/lyx)\
**Post date:** [February 6, 2026, 1:06am UTC](https://forum.cursor.com/t/cursor-headless-mode-supports-persistent-processes/150983/1 "2026-02-06T01:06:31Z")

</div>

### Feature request for product/service

Cursor CLI

### Describe the request

In headless mode, each time a conversation begins, a new process is started. Starting a new process involves a cold start, resulting in long processing times. Is it possible to support background processes running continuously?

---

<div class="post-metadata">

**Author:** ![Michael\_Kufner](https://avatars.discourse-cdn.com/v4/letter/m/c89c15/32.png) [@Michael\_Kufner](https://forum.cursor.com/u/Michael_Kufner)\
**Post date:** [March 5, 2026, 9:27pm UTC](https://forum.cursor.com/t/cursor-headless-mode-supports-persistent-processes/150983/3 "2026-03-05T21:27:41Z")

</div>

Hello, I would appreaciate the same. We are running cursor-cli as a headless process on our architecture (Slack connection, when employees could ask about internal implementation details like “how XY works”). Each time when user asks, headless-cli is cold started. It would be great if something like “–resume” works also on headless mode 🙂