Before submitting
Area
apps/desktop
Steps to reproduce
- use the terminal
- some combination of restarts / version changes / upgrades / computer restarts (really unclear)
- open terminal to see a bunch of escape codes typed in the terminal
Expected behavior
terminal restores to previous state without escape codes
Actual behavior
common to see escape codes in a restored terminal (the majority of my threads)
t3code-278c6346 on git ci/add-generated-attributes [$] via node 25.8.1 on aws company
> 10;rgb:f5f5/f5f5/f5f511;rgb:1616/1616/16161;2c10;rgb:f5f5/f5f5/f5f511;rgb:1616/1616/16161;2c10;rgb:f5f5/f5f5/f5f511;rgb:1616/1616/16161;2c
t3code-278c6346 on git ci/add-generated-attributes [$] via node 25.8.1 on aws company
> ^[]10;rgb:f5f5/f5f5/f5f5^[\^[]11;rgb:1616/1616/1616^[\^[[?1;2c^[]10;rgb:f5f5/f5f5/f5f5^[\^[]11;rgb:1616/1616/16
t3code-278c6346 on git ci/add-generated-attributes [$] via node 25.8.1 on aws company
> 10;rgb:f5f5/f5f5/f5f511;rgb:1616/1616/16161;2c10;rgb:f5f5/f5f5/f5f511;rgb:1616/1616/16161;2c
Impact
Cosmetic issue
Version or commit
0.0.13
Environment
macos 26.3, installed via homebrew
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
ctrl+c to get a new line and ignoring it
Before submitting
Area
apps/desktop
Steps to reproduce
Expected behavior
terminal restores to previous state without escape codes
Actual behavior
common to see escape codes in a restored terminal (the majority of my threads)
Impact
Cosmetic issue
Version or commit
0.0.13
Environment
macos 26.3, installed via homebrew
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
ctrl+c to get a new line and ignoring it