Warpified tsh subshell occasionally prints massive numeric DCS string instead of normal command output #8702
Description
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 I manually warpify a tsh subshell (I turned off auto-warpify for all terminals because I need it only for chosen) and run regular commands, Warp sometimes prints a huge line of hexadecimal‑looking digits (what appears to be the raw Device Control String) into the terminal output.
The same command, re‑run a second later in the same session, produces normal output without the extra line.
This looks like Warp’s subshell DCS sequence being echoed/rendered instead of being intercepted and handled internally.
Here I ran the "history | grep bouncer" command. The first time, I got a bunch of numbers along with the expected output; the second time, I got only the expected output:
(partly sanitized, as I’m not sure what it is exactly)
To reproduce
To reproduce
1. On macOS, open Warp.
2. Start a remote session using tsh (Teleport) to a Linux host.
3. In that tsh session, click “Warpify” (I do not use automatic warpify; it is triggered manually).
4. Run normal interactive commands, for example:
• history | grep
• git status or other short commands.
5. Observe that occasionally, instead of just the expected command output, Warp prints a single extremely long line consisting of digits/hex characters before or in place of the usual output.
6. Immediately repeat the same command; now it runs normally with no extra line.
The behavior is intermittent, but it happens often enough during a day of work to be very noticeable.
Expected behavior
Warp should intercept and handle its DCS / warpify control sequences internally so that they are never rendered into the visible terminal output. Commands in a warpified tsh subshell should display exactly the same user‑facing output as in a non‑warpified session, without long numeric garbage lines.
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
macOS Tahoe 26.2 (25C56)
Shell Version
No response
Current Warp version
v0.2026.02.11.08.23.stable_01
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
The same issue was also reproducible on previous Warp versions.
Additional context
I do not use automatic “Warpify subshells”; I always warpify manually only for specific terminals where I need Warp features.
Given the documentation that warpify uses a DCS string printed into the shell to signal subshell start, this looks like that control string sometimes leaks into the visible output stream instead of being consumed by Warp.
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