#16629
Issues/warpdotdev/warp/#16629

Tab completion for file names does not work for fresh editor

Opensgon00opened 7d ago

Pre-submit Checks

Describe the bug

When I use fresh editor, the tab completion for file names does not work. I tried other normal terminals, they work fine.

To reproduce

Tab completion for file names does not work for fresh editor. For example, type fresh file-name-[TAB], nothing happens.

Expected behavior

No response

Screenshots, videos, and logs

No response

Operating system (OS)

Linux

Operating system and version

Fedora 44

Shell Version

No response

Current Warp version

No response

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

No response

Activity

5
warp-for-oss[bot]7d ago

@sgon00

Here's what I found while triaging this issue:

Thanks for the report. This looks like a Warp-specific file-name completion failure for the Fresh terminal editor on Linux; the reproduction is plausible, but the Warp version and shell context are needed to narrow down the completion path.

I have a few follow-up questions before I can narrow this down:

  1. Which Warp version and channel are you using when fresh file-name-[Tab] does nothing?
  2. Which shell is active in that Warp session where the Fresh completion fails?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that fresh editor filename Tab completion appears to fail only in Warp on Linux, likely in the terminal completion/native shell completion path, but key environment details are missing..

Triage summary

  • The report describes a Warp-only Linux completion issue: typing fresh file-name-[TAB] does nothing for the Fresh terminal editor, while other terminals complete file names.
  • This belongs in area:completions and os:linux; it is not marked high priority because the reporter explicitly says it is not a regression and there is no crash, data loss, or security impact.
  • Reproducibility is medium: the command pattern is clear, but the report is missing Warp version/channel, shell/shell version, logs, and any setting context.

Code notes

  • app/src/terminal/input.rs handles Tab via input_tab, opens completion suggestions, and resolves completion sources in run_completions_async / resolve_completion_sources.
  • When native shell completions are enabled, explicit Tab can run bundled completions first and then dispatch native shell completions if bundled results are empty. Tests in app/src/terminal/input_tests.rs document that an unrecognized command is sent to the shell rather than immediately falling back to file-path completions.
  • Native completion requests are routed through app/src/terminal/writeable_pty/pty_controller.rs and results are collected by app/src/terminal/model/terminal_model.rs. Generic file-path fallback lives in crates/warp_completer/src/completer/suggest/mod.rs and crates/warp_completer/src/completer/engine/argument/legacy.rs.
  • Closest open issues found during dedupe were #2719, #5708, #13380, and #16206, but they describe broader or different completion symptoms; fewer than two candidates match this Fresh-specific filename-completion no-op closely enough to mark duplicate.

What is still needed

The missing Warp version/channel and shell context are needed to determine whether this is a native shell completion bridge problem, a generic path-completion fallback gap for unknown commands, or Fresh-specific shell completion behavior.

Question reasoning

  1. Which Warp version and channel are you using when fresh file-name-[Tab] does nothing? — The issue body leaves Current Warp version blank, and completion behavior has changed across releases and channels.
  2. Which shell is active in that Warp session where the Fresh completion fails? — Warp's native and fallback completion paths are shell-sensitive, and the Shell Version field was left blank.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

sgon007d ago

warp version: v0.2026.09.16.08.27.stable_02 shell: bash. (default shell)

echo $SHELL /bin/bash

warp-for-oss[bot]7d ago

@sgon00

Here's what I found while triaging this issue:

Thanks for the Warp version and shell details. This looks like a Warp completions/input issue on Linux+bash, but one or two setting-specific checks are needed to narrow whether Tab is not invoking completions or whether native shell completions are blocking the path fallback.

I have a few follow-up questions before I can narrow this down:

  1. With the cursor after the same fresh file-name- text, does pressing Ctrl-Space open file-name completions?
  2. If you temporarily turn off Native shell completions in Warp settings, does fresh file-name-<Tab> start completing file names?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that linux/bash report that file-name Tab completion does not open or insert matches for the fresh editor command in Warp..

Triage summary

This is a Warp completions/input bug report on Linux: in Fedora 44 with bash and Warp Stable v0.2026.09.16.08.27.stable_02, pressing Tab after a partial file name for the fresh editor command reportedly does nothing, while comparable terminals complete the path.

The most relevant code path is the terminal input completion flow and bash/native completion fallback:

  • app/src/terminal/input.rs handles Tab, completion source selection, native-shell dispatch, and fallback to path completions.
  • app/assets/bundled/bootstrap/bash_body.sh implements warp_run_generator_command_native_completions for bash.
  • crates/warp_completer/src/completer/suggest/mod.rs and crates/warp_completer/src/completer/engine/path.rs provide the Warp-side file-path fallback.
  • app/src/settings/input.rs exposes the Warp completions, native shell completions, completions-while-typing, and input-mode settings that can affect this behavior.

The likely cause is still uncertain. The code is intended to fall back to Warp file-path suggestions when native shell completion returns no matches, so the next useful discriminator is whether this is a Tab keybinding/input-mode issue or a native-shell-completion interaction specific to fresh.

Duplicate search

I fetched all open issues and compared completion/path-related reports. I found related path-completion issues such as #2274, #13380, #16206, #11864, #4899, and #1794, but fewer than two existing issues match this exact Linux/bash fresh file-name Tab no-op report closely enough to mark it as a duplicate.

Follow-up needed

The reporter's added comment supplied the Warp version and shell, which closes two common environment gaps. Two remaining setting-specific checks should determine the likely owner/fix path.

Question reasoning

  1. With the cursor after the same fresh file-name- text, does pressing Ctrl-Space open file-name completions? — Warp can remap Tab away from opening completions, so this checks whether the completion menu is available through the alternate default binding without asking for information the codebase can provide.
  2. If you temporarily turn off Native shell completions in Warp settings, does fresh file-name-<Tab> start completing file names? — The code has separate Warp and native-shell completion paths; this answer would distinguish a bash native-completion interaction from Warp's general path-completion fallback.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

sgon007d ago

1, Ctrl-space is bind to fcitx5 input method for switching between different input methods. Thus it won't work. 2, After temporarily turning off Native shell completions in Warp settings, it does solve the issue and fresh editor starts completing file names.

warp-for-oss[bot]7d ago

@sgon00

Here's what I found while triaging this issue:

Thanks for the follow-up. Since disabling Native shell completions makes fresh file-name<Tab> complete filenames again, this looks specific to Warp's native-completion path rather than a general Fresh editor issue. That setting is a reasonable workaround while the native-completion behavior is investigated.

Maintainer details

I concluded that fresh filename Tab completion on Linux/bash appears to fail only when Warp's Native shell completions path is enabled..

Triage summary

This is a Linux/bash completion bug affecting filename completion for the fresh editor command when Warp's Native shell completions setting is enabled. The reporter's follow-up supplies the previously missing Warp version (v0.2026.09.16.08.27.stable_02) and shell (bash), and says disabling Native shell completions makes fresh file-name<Tab> complete filenames again.

Likely area

The strongest signal is that toggling Native shell completions changes the behavior. In app/src/terminal/input.rs, manual Tab requests resolve to CompletionSources::WarpThenNative or CompletionSources::NativeOnly when terminal.input.native_shell_completions_enabled is on. That path defers normal file-path fallback while it asks the shell and then converts native completion output through native_shell_suggestion_results. Bash native completions are generated by warp_run_generator_command_native_completions / _warp_native_bash_completions in app/assets/bundled/bootstrap/bash_body.sh.

fresh does not appear to have a bundled Warp command signature in command-signatures-v2, so Warp should ultimately fall back to filesystem path suggestions for its filename argument. The reporter's workaround suggests the native Bash-completion path is either returning/handling results in a way that suppresses visible filename suggestions or otherwise preventing the fallback from applying for this command.

Duplicate check

I enumerated open issues and checked recently closed issues from the last seven days. #16206 is closely related because it also involves Native shell completions disrupting path completion and has the same workaround, and #16223 is a related recent path-completion report, but neither matches this exact Fresh/Linux/bash failure closely enough to satisfy the repository's duplicate threshold.

Follow-up status

The reporter's follow-up answered the missing Warp version/shell details and identified a targeted workaround, so I would remove needs-info for now. Further debugging should reproduce fresh file-name<Tab> on Linux/bash with Native shell completions enabled and compare the shell generator output against the Warp file-path fallback.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz