[FEATURE]: Configurable confirmation before exiting with Ctrl+D on macOS

[silvioprog]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem

I use OpenCode on macOS with Ghostty, and I accidentally exit OpenCode several times a day by pressing Ctrl+D.

Ctrl+D is deeply ingrained in my terminal workflow, and when working with long-running agent sessions it's easy to hit it unintentionally, immediately terminating the session.

Comparison

I don't experience this with Claude Code, Codex CLI, or Kimi Code, since they require an additional action (such as confirmation or a second key press) before exiting, making accidental termination much less likely.

Proposal

Would it be possible to make exit confirmation configurable?

For example, one of the following:

• Require pressing Ctrl+D twice within a short timeout.
• Show a confirmation prompt before exiting.
• Add a configuration option (e.g. confirm_exit: true).
• Allow users to disable or remap Ctrl+D for app_exit independently.

This would preserve the current default behavior while allowing users who frequently hit Ctrl+D by accident to avoid losing active agent sessions.

Note: This is not a duplicate of the Ctrl+C discussions. This request is specifically about accidental exits caused by Ctrl+D on macOS.

[github-actions]

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

You may also want to look at #40331 ([FEATURE]: Add configurable TUI keybind for auto-approve permissions), which touches on the broader topic of configurable TUI keybindings.

[silvioprog]

I was able to work around the issue by removing Ctrl+D from app_exit:

{
  "keybinds": {
    "app_exit": "ctrl+c,<leader>q"
  }
}

That prevents accidental exits, but it also completely disables Ctrl+D as an exit shortcut.

My feature request is slightly different: I'd like to keep Ctrl+D available while making accidental exits less likely, for example with an optional confirmation or requiring a second Ctrl+D within a short timeout.

So the keybinding customization is a good workaround, but it doesn't address the underlying request.