[FEATURE]: Require double Ctrl+C to exit the CLI (first press interrupts, second exits)

Describe the enhancement you want to request

Currently, pressing Ctrl+C immediately exits the entire OpenCode CLI. This is surprising and disruptive — it's easy to accidentally exit during a long session.

Claude Code and Codex both use a two-press pattern:

First Ctrl+C — interrupts the current agent action / cancels the in-progress operation
Second Ctrl+C — exits the CLI entirely

OpenCode should adopt the same behavior. This gives users a safe escape hatch for cancelling operations without losing their session context.

The first Ctrl+C could show a message like "Press Ctrl+C again to exit" so the user knows what's happening.

Suggested implementation path

In the TUI key handler, intercept the first Ctrl+C as a session interrupt (same as Esc or /exit light)
On a second Ctrl+C within a short window (e.g., the same keybind cycle or within a few seconds), trigger the full exit
Optionally display a brief toast/hint after the first press

Additional context

Related issue (clarifying docs): #23478

This issue might be a duplicate of existing issues. Please check:

[FEATURE]: Require double Ctrl+C to exit (like Claude Code) #15932: [FEATURE]: Require double Ctrl+C to exit (like Claude Code) — identical request
[FEATURE]: Can use ctrl+c twice to close the tui? #10975: [FEATURE]: Can use ctrl+c twice to close the tui? — same feature request
Feature: Double Ctrl+C to Quit (Codex CLI-style interrupt handling) #9041: Feature: Double Ctrl+C to Quit (Codex CLI-style interrupt handling) — same feature request (closed)
Add confirmation prompt before exiting on Ctrl+C #23584: Add confirmation prompt before exiting on Ctrl+C — very closely related
[FEATURE/BUG] Ctrl+C should ask for confirmation before quitting and clearing the session #23323: [FEATURE/BUG] Ctrl+C should ask for confirmation before quitting — closely related

For keybind-related issues, please also check our pinned keybinds documentation: #4997

You can change the default keybindings to something else. ctrl+c only exits when the prompt is empty. I have remapped mine for this reason, but changing the default binding or behaviour would just make everybody else complain.

ctrl+c only exits when the prompt is empty.

That was not enough.

Every time I hit Ctrl + C while opencode was working with an empty prompt, the damn program quit. It's weird and dangerous.

Why do you deliberately go against what most agents do?

This double-Ctrl-C request has been brought up a ridiculous amount of times. Why can it not at least be a config option?

feat(tui): require double Ctrl+C to quit

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Navigation Menu

Repository navigation

[FEATURE]: Require double Ctrl+C to exit the CLI (first press interrupts, second exits) #26371

Describe the enhancement you want to request

Suggested implementation path

Additional context

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[FEATURE]: Require double Ctrl+C to exit the CLI (first press interrupts, second exits) #26371

Description

Describe the enhancement you want to request

Suggested implementation path

Additional context

Activity

github-actions commented on May 8, 2026

kommander commented on May 11, 2026

verils commented on May 21, 2026

CharlesMcquade commented on May 24, 2026

github-actions commented on Jul 24, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions