Cursor CLI's Ctrl+O doesn't work in tmux

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

As title, opening the output detail with Ctrl+O within tmux doesn’t work

Steps to Reproduce

Run Cursor CLI in tmux and try to open output details with Ctrl+O

Operating System

MacOS

Version Information

CLI Version 2026.03.20-7da3412
OS darwin (arm64)
Terminal ghostty
Shell bash

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

If you don’t use window rotation in tmux since it’s bound to C-o you can remove it from inside terminal:

tmux unbind-key -T prefix C-o

Or add it in the .tmux.conf

I don’t know if that will solve the problem as I haven’t tested it but that’s usually the case of what happens inside screen/tmux.

Worst case you can C-b then C-o and see (or whatever your tmux escape key is set to)

8

Hi @bao,

Thanks for reporting this. We’re aware of issues with the Ctrl+O compact toggle in certain terminal environments, including tmux.

To help narrow down the root cause, please clarify one thing: when you press Ctrl+O inside tmux, does absolutely nothing happen, or does the screen flash/flicker/reload without showing the expanded output? This distinction helps us determine whether the key isn’t being received at all, or if the re-render after the toggle is breaking in tmux.

Also: does Ctrl+O work when running the CLI directly in Ghostty (outside of tmux)? This would confirm whether the issue is tmux-specific.

In the meantime, a couple of things to try:

  1. Enable extended keys in tmux to improve key sequence passthrough. Add to your .tmux.conf:

    set -g extended-keys on
set -as terminal-features 'xterm-256color:extkeys'

    Then reload with tmux source-file ~/.tmux.conf.

  2. As @f00z suggested, you can also try unbinding C-o from tmux to rule out any interception:

    tmux unbind-key -T prefix C-o

Our team is aware of this and related CLI+tmux interaction issues.

11

Ah for some reason it works now. Maybe it was a transient issue. Thanks!

1 Like