Composer agent sending interrupts (^C) for long runs

Support Bug Reports
1

:white_check_mark: Check the forum to ensure the issue hasn’t been reported already
Not seeing this
:lady_beetle: Provide a clear description of the bug
I often ask the agent to run my test suite which can take a few minutes. It recently started send ^C to interrupt the process before it was done. Is there a timeout I can configure?

:arrows_counterclockwise: Explain how to reproduce the bug (if known)
Ask the agent to run a large test suite. Mine happens to run in docker.

:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).

image
image748×443 27.8 KB

:computer: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Mac Sequoia 15.1
Version: 0.45.7
VSCode Version: 1.96.2
Commit: 6ea842450e04c5537da4d83d51823fae13bb30f0
Date: 2025-01-30T18:32:32.733Z (2 days ago)
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.1.0

:no_entry_sign: Tell us if the issue stops you from using Cursor.
Makes it a little less effective since I can’t trust it to allow the tests to run to completion

1 Like
2

Hey, we are working on this but I’d recommend adding this to your .cursorrules as an instruction, which should hopefully stop or reduce the times this happens!

3

Thank you for raising this, I have the same issues when using terraform’s apply command (also long running).

@danperks, what exactly do you recommend adding to .cursorrules as an instruction?

1 Like
4

Hey, it can require a bit of experimentation, but something like When running commands, do not EVER terminate the command with CTRL+C / SIGINT. I will manually terminate it if needed might work?

1 Like
5

Just added something to that effect, but I now have to confess it stopped doing it prior to me making that change. One of many ¯\(ツ)/¯