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?
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
