Ctrl+I doesn't work for filename completion

[ryofurue]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

[I did search both "Warp bugs" and "Warp known issues page" but I may well have missed duplicates as I don't know exactly how to search for Ctrl+I. I just search for "Ctrl+I".]

As the title says, Ctrl+I doesn't work for filename completion.

I asked your AI assistant and it generated the following report.

[Below you ask if this issue prevents me from using Warp . . . I just habitually type Ctrl+I to mean Tab. It's a muscle memory for more than 20 years.]

To reproduce

1. The behavior you're experiencing:
   • Tab works for filename completion
   • Ctrl+I doesn't work for filename completion
   • Both keys generate the same ASCII character (0x09) as shown in our testing
   • Both are correctly bound to expand-or-complete in zsh
2. The test results we gathered:
   • The bindkey output showing "^I" expand-or-complete
   • The xxd test showing both keys generating 0x09

Expected behavior

3. Your expectation:
   • Since Tab and Ctrl+I traditionally generate the same ASCII character, they should behave identically for shell completion

Screenshots, videos, and logs

No response

Operating system (OS)

macOS

Operating system and version

macOS 15.3.2

Shell Version

zsh 5.9 (arm64-apple-darwin24.0)

Current Warp version

v0.2025.03.26.08.10.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[acarl005]

Keybinding search is space-separated, e.g. "cmd i" or "ctrl i". We don't have "ctrl i" bound by default. Have you tried setting that in Settings > keyboard shortcuts?

[ryofurue]

We don't have "ctrl i" bound by default.

So, "ctrl i" and Tab are differentiated and that's intentional . . . .

Have you tried setting that in Settings > keyboard shortcuts?

I've just tried: I've set "Open Completion Menu" to "^I". Now, "ctrl i" does open the completion menu, but to go to the next candidate, you still need to press Tab.

(But, how do you assign multiple keys to a single action?)

In "Settings" > "Keyboard shortcuts", I don't see other actions that Tab is assigned to.

If the list of the completion candidates is long, you use "ctrl n" and "ctrl p" to navigate in the list, but if the list is short, I just want to keep pressing "ctrl i".

In the default setting, you keep pressing Tab to move down the list and Shift+Tab to move up the list. Are these keys customizable? To move down the list, both "ctrl n" and Tab work.

By the way,

Keybinding search is space-separated, e.g. "cmd i" or "ctrl i"

I suppose you mean that you type "cmd i" to search for it in "Settings" > "Keyboard shortcuts". I see. Thanks.

But, when I said I didn't know how to search for shortcut keys, I meant that I didn't/don't know how to search for those in this github issue tracker. Does the search engine treat "+" as a special character, should it be "Ctrl" or "Ctl" ? etc.

[acarl005]

"ctrl i" does open the completion menu, but to go to the next candidate, you still need to press Tab

Ah this is a good point. We should fix that.

But, when I said I didn't know how to search for shortcut keys, I meant that I didn't/don't know how to search for those in this github issue tracker. Does the search engine treat "+" as a special character, should it be "Ctrl" or "Ctl" ? etc.

I don't think GH provides a nice way to search these unfortunately.