[Windows] CTRL_C_EVENT not handled by bun (umbrella issue)

This is to collect issues that are reporting ANSI escape sequences after CTRL+C in some windows terminals and shell, where it sends a CTRL_C_EVENT which is not handled by bun.

Pressing Ctrl+C in input field outputs ANSI escape sequences/garbled text #7062
Ctrl+C does not disable mouse tracking, causing raw escape sequences to flood terminal (Windows) #6912

This umbrella issue appropriately collects ANSI escape sequence issues related to CTRL_C handling. Additional related issues found:

In the Windows system, pressing Ctrl+C will automatically exit the terminal #6189: In the Windows system, pressing Ctrl+C will automatically exit the terminal
Bug: Ctrl+C interruption in opencode causes terminal corruption with ANSI escape sequences #5990: Ctrl+C interruption causes terminal corruption with ANSI escape sequences
Provide a way to stop all running scripts when OpenCode is interrupted #3057: Ctrl+C should terminate child processes
Provide means to disable Ctrl-C #2999: Provide means to disable Ctrl-C (Windows quits app instead of copy)
bug: ctrl+c exiting app even when prompt input isn't empty #5071: Ctrl+C exiting app even when prompt input isn't empty

All of these appear to stem from improper CTRL_C_EVENT and signal handling on Windows. The umbrella issue structure is good for tracking the root cause.

on windows bun, the ctrl+c sigint gets sent to all process+childprocess, so the bun run wrapper instantly kills its child.
i need to check what happens with the published app too...
i have a bun wip branch that is a poc fixing this, but it janky.
not sure its something opentui/opencode can handle as a workaround if its parent process is killing it

Is this issue for collecting reports until the Bun team fixes it or are temporary workarounds in OpenCode also accepted?

I have submitted a PR to the Bun team resolving this for us

oven-sh/bun#25876

I am seeing about adding tests.
Also need to investigate the wider impact of this change.
So there's more for me to do on this PR.
Hoping for guidance from the Bun team tho.

oven-sh/bun#25876

I am seeing about adding tests. Also need to investigate the wider impact of this change. So there's more for me to do on this PR. Hoping for guidance from the Bun team tho.

Thanks for doing this! I press Ctrl+C out of habit and get kicked out 4-5x a day. Ugh.

Any progress on this?

I noticed that it only appears after update check, and that autoupdate: false doesn't properly skip it currently.

Issue: Ctrl-C doesn't clear the input on Windows, it crashes #10538
PR to fix the early exit: fix(tui): Ensure version check is skipped when autoupdate is disabled #10905

With that PR + autoupdate: false Ctrl+C just works as expected.

I'd be happy if someone could look into it.

Yes, early next week a beta build will be running a bun fork which fixes the root cause :)

Come on, boss!

ctrl+c handling is now in as of 1.1.60

Works for me now. Thanks!

ctrl+c handling is now in as of 1.1.60
How?

Navigation Menu

[Windows] CTRL_C_EVENT not handled by bun (umbrella issue) #7074

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Windows] CTRL_C_EVENT not handled by bun (umbrella issue) #7074

Description

Activity

github-actions commented on Jan 6, 2026

Hona commented on Jan 6, 2026

val-2 commented on Jan 8, 2026

Hona commented on Jan 8, 2026

Hona commented on Jan 8, 2026

carljuneau commented on Jan 15, 2026

tnglemongrass commented on Feb 5, 2026

Hona commented on Feb 6, 2026

xiongxingplus commented on Feb 6, 2026

Hona commented on Feb 12, 2026

carljuneau commented on Feb 13, 2026

alMubarmij commented on Mar 6, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions