Uh oh!
There was an error while loading. Please reload this page.
fix: app_exit keybind ignored when using <leader> (including default <leader>q) - #8151
fix: app_exit keybind ignored when using <leader> (including default <leader>q)#8151razor-x wants to merge 1 commit into
Conversation
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
f1ae801 to
08fa7f7Compare176c3e7 to
0c5f404Compare57d3933 to
938c5ecCompare6b265d7 to
ec3ac3cComparerekram1-node
commented
May 15, 2026
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Fixes#3851
What does this PR do?
Summary
Why this fixes it
How did you verify your code works?
Built and ran locally, verified q exits the app as expected.
I was not able to find a way to add an test for this. The core issue depends on the
app.tsxrunning and focus passing between the prompt an the app, so a unit test is mostly ceremonial. An e2e test would require a net test harness to mount the TUI app similar to how playwright e2e works.