Preventing Accidental OpenCode Exits with Ctrl+C

A developer has documented a configuration workaround for OpenCode that prevents accidental session loss when users press Ctrl+C out of terminal habit. By remapping the app_exit keybinding in the OpenCode configuration file to Ctrl+D or a leader-based shortcut, the interrupt command no longer closes the entire application. The change separates interrupting a running process from exiting the AI coding agent, preserving long sessions with valuable context.

OpenCode is powerful, but one default behavior kept getting in my way: pressing Ctrl + C could close the application itself. If you spend a lot of time in terminals, Ctrl + C is muscle memory. You press it to interrupt a command, stop a long-running process, or simply because your hands move before you think. Losing the whole OpenCode session because of that is frustrating. The fix is simple: move the application exit action to a different keybinding. Open your OpenCode configuration file and customize the keybindings. For example: { "keybinds": { "app exit": "ctrl+d,<leader q" } } With this configuration, Ctrl + C is no longer the application-exit shortcut. You can then use Ctrl + D or the leader-based shortcut to exit intentionally. AI coding agents often stay open for long sessions with valuable context. A keybinding that is common for interruption in terminal workflows should not unexpectedly destroy that session. Separating "interrupt what is happening" from "close the entire application" makes the interface much harder to use incorrectly. This is a tiny configuration change, but it removed one of the most annoying sources of accidental session loss for me. If you use OpenCode inside a terminal and frequently hit Ctrl + C out of habit, remapping app exit is worth doing early.