# Resume agent mode after long running processes

**URL:** <https://forum.cursor.com/t/resume-agent-mode-after-long-running-processes/137047>\
**Category:** Feature Requests\
**Created:** [October 11, 2025, 10:34am UTC](https://forum.cursor.com/t/resume-agent-mode-after-long-running-processes/137047 "2025-10-11T10:34:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Keith\_Kam](https://avatars.discourse-cdn.com/v4/letter/k/46a35a/32.png) [@Keith\_Kam](https://forum.cursor.com/u/Keith_Kam)\
**Post date:** [October 11, 2025, 10:34am UTC](https://forum.cursor.com/t/resume-agent-mode-after-long-running-processes/137047/1 "2025-10-11T10:34:53Z")

</div>

### Feature request for product/service

Chat

### Describe the request

I am working on a variety of scientific data pipelines and would like the ability to customize how agent resumes after a process it invokes. My development loop looks something like:

1. write a long prompt that details the implementation plan
2. let cursor write code and invoke the pipeline locally (via a custom cli)
3. let cursor inspect the output in structured logs (grep, jq, awk) and inspect the data (duckdb)

The challenge I have at the moment is being able to configure long running tools as this often times out if we make this blocking. Instead we have a run launch command and a run status command, and we let cursor poll the status until it is ready to analyse (with optional timeouts for the run).

This doesn’t seem particularly efficient and I would rather be able to invoke a call back to tell cursor to “resume agent” on the finishing of the command. Alternatively this could look like background commands (in which case I can just design a sync api instead).

---

<div class="post-metadata">

**Author:** ![vimmaxxer3000](https://avatars.discourse-cdn.com/v4/letter/v/8797f3/32.png) [@vimmaxxer3000](https://forum.cursor.com/u/vimmaxxer3000)\
**Post date:** [August 8, 2026, 3:54am UTC](https://forum.cursor.com/t/resume-agent-mode-after-long-running-processes/137047/2 "2026-08-08T03:54:09Z")

</div>

Hi Keith, were you able to figure out anything in regards to this?
