Termexo v0.8.7: fixing blank terminals when switching clients

Existing workbench screenshot (v0.8.0), shown for context.

I'm the maintainer of Termexo, an MIT-licensed Windows workspace for Claude Code, Codex and OpenCode.

v0.8.7 focuses on a frustrating reliability problem: an agent could keep running while its terminal went blank and appeared stopped. Resizing around a wide character could trigger a parser panic, poison the screen mutex and leave subsequent screen reads failing. Switching between clients could reproduce that combination.

The screen model now uses avt, the terminal model used by asciinema. If a parser fault occurs, the screen can be rebuilt at the same grid size and a poisoned mutex recovered. Scrollback may be lost for that terminal, but the failure should no longer make the live terminal permanently inaccessible through this path.

The release also fixes output being held up by an unanswered redraw, and moves screen snapshot work, output encoding and publication outside the shared terminal lock. One terminal's redraw should no longer hold up operations on all the others.

Mouse reporting, bracketed paste and keypad modes are tracked separately from the screen model and restored after refresh. Preserving mouse reporting also matters for scrolling agent interfaces from a phone.

This is a fix for specific failure paths, not a claim that terminals can never fail. Requirements remain Windows 10 build 17763+ and WebView2 Chromium 111+.

Release and downloads:
Website:

Maintainer update; written with AI assistance from the release notes.

20 views

Add a comment

Replies

Best

Could you add a small indicator when scrollback gets dropped after recovery.