You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
Open the project.
Open the integrated terminal.
Repeat closing and reopening the terminal several times.
Occasionally, the terminal starts with garbled output containing visible ANSI escape sequences.
Expected behavior
The terminal should interpret ANSI escape sequences correctly and display the prompt and startup output with normal formatting.
Actual behavior
The terminal sometimes prints ANSI escape/control sequences as plain text, for example sequences beginning with characters such as:
^[4;...
^[38;...
^[15;...
This causes the startup output and prompt to appear corrupted. Exiting the active shell via ctrl+x or ctrl+c doenst work. After terminating and reopening the terminal, it usually works normally again. This happened after running bun run dev on a nextjs project.
Before submitting
Area
apps/desktop
Steps to reproduce
Expected behavior
The terminal should interpret ANSI escape sequences correctly and display the prompt and startup output with normal formatting.
Actual behavior
The terminal sometimes prints ANSI escape/control sequences as plain text, for example sequences beginning with characters such as:
^[4;...
^[38;...
^[15;...
This causes the startup output and prompt to appear corrupted. Exiting the active shell via ctrl+x or ctrl+c doenst work. After terminating and reopening the terminal, it usually works normally again. This happened after running bun run dev on a nextjs project.
Bildschirmaufnahme.2026-07-28.um.20.22.17.mov
Impact
Minor bug or occasional failure
Version or commit
0.0.30-nightly.20260728.931
Environment
macOS 26.3
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
terminating the shell completly