Is there any way to configure maxInterruptSignals?

[dorian-marchal]

Hi, I would like my task to be killed right away when pressing ^C, can I do that?

^Ctask: Signal received: "interrupt"
^Ctask: Signal received: "interrupt"
^Ctask: Signal received for the third time: "interrupt". Forcing shutdown

[wellkilo]

No, this is not configurable in current Task. The interrupt count is a compile-time constant:

const maxInterruptSignals = 3

Task intercepts SIGINT, SIGTERM, and SIGHUP; the first two signals allow running processes time to clean up, and the third calls os.Exit(1). See signals.go. There is currently no Taskfile key, CLI flag, or environment variable that changes that threshold.

If you truly need immediate termination in CI, the supervisor should enforce it rather than relying on interactive Ctrl-C behavior. For example, send SIGKILL to the task process group after your own timeout (with the usual warning that this bypasses cleanup). For normal terminal use, pressing Ctrl-C three times is the supported forced-shutdown path.

Changing this per invocation would require a Task feature/code change: expose the constant as configuration and define whether it applies globally or per running task. If the answer to the current behavior is sufficient, please mark this as accepted; otherwise this discussion can serve as the feature request for a configurable threshold.