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
Setting up pytermwm's MCP server in LM Studio and other MCP clients, with a debugging checklist
(docs/api.md).
Changed
Background effects are much cheaper: at most 20 frames per second, far less redrawn per frame, and every frame is
sent as one synchronized update. On a 200x55 screen matrix went from 37% to 7% CPU and plasma from 262% to 11%.
new-window -- PROG ARG... (and pytermwm run -- PROG ARG...) starts the program directly with exactly these
arguments instead of through the shell. A single argument is still a shell command line.
Fixed
While a background effect runs, the screen is no longer redrawn as fast as possible, and the cursor is no longer
hidden and shown again on every frame (it looked like very fast blinking and made windows lag).
MCP tools report "no pytermwm session ... is running" (and how to start it) instead of an internal error.
Running pytermwm (or python ptw.py) inside a pytermwm window no longer attaches the session to itself and
crashes the window manager: it is refused with a hint. Attaching to another session from inside needs --nested.
Windows: programs in a window wrote to pytermwm's own redirected output (the daemon's log file) instead of
the window.
Windows: pytermwm run -- python ... failed in PowerShell, the default shell.
The status line could disappear after reattaching until the terminal was resized.
In the command palette, effect none ran effect list instead of stopping the background effect.
An inactive window no longer shows the bell sign ␇ when its prompt only sets the window title, or the
activity dot ● when its shell redraws the prompt after a resize.