Autocomplete suggestion corrupts non-ASCII UTF-8 characters (e.g. Turkish "ü") in path names

[baranbingol1]

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 an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

When Warp's autocomplete suggests a path that contains non-ASCII UTF-8 characters
(e.g. Turkish characters like "ü", "ş", "ğ", "İ"), accepting the suggestion inserts
a corrupted/broken version of the character instead of the correct one.

For example, a folder named "Masaüstü" (Turkish word for "Desktop") is suggested
by autocomplete, but when the suggestion is accepted, the "ü" character is broken/
garbled, resulting in a command like cd Masa??st? or similar — which then fails
to execute because the path doesn't resolve correctly.

This makes it impossible to navigate to or work with any directory or file that
contains non-ASCII characters via autocomplete.

Related historical issue: #985 (closed 2022) reported a similar problem with
Turkish characters, but the bug appears to have regressed or was not fully resolved
for this specific autocomplete acceptance flow.

To reproduce

1. Create a directory with a non-ASCII UTF-8 character in its name:
   mkdir Masaüstü
2. In the Warp terminal, start typing:
   cd Mas
3. Wait for the autocomplete suggestion to appear showing "Masaüstü"
4. Accept the suggestion
5. Observe that the accepted text contains a corrupted/broken character instead of "ü"
6. Press Enter — the command fails because the path cannot be resolved

Expected behavior

When accepting an autocomplete suggestion for a path containing non-ASCII UTF-8
characters (e.g. "Masaüstü"), the full correct path should be inserted into the
input — with all characters intact — and the command should execute successfully.

Screenshots, videos, and logs

Operating system (OS)

Windows

Operating system and version

Windows 11

Shell Version

Powershell 5.1.26100.7920

Current Warp version

v0.2026.04.01.08.39.stable_01

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?

No

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

[oz-by-warp]

We need a bit more information before we can continue triaging this issue.

If you're still hitting this, could you try reproducing it on the latest version of Warp and share logs along with a screenshot or short video if possible?

If there's no activity after 3 business days, we'll close this out to help keep the tracker tidy.

---

This is part of an automated backlog review and may be inaccurate. If you believe this assessment is wrong, please let us know.