Claude Code 2.1.286〜2.1.288 Mods hit five desktop breakages

The report frames the problems as a surface mismatch rather than a bug in any single component. On startup, the author found that an open triggered by human action (a command, a submitted prompt, a button) is placed at any width, while an open with nothing human behind it — from session.start or from a clock — needs 144 columns, and a pane a person has already opened needs 110. Because desktop may simply refuse to place a startup pane, the author's workaround sets a flag and re-opens the pane on the first prompt submission, checking the event origin for 'composer' or 'bridge'. The narrowing also shows up in the app's own behavior: the author notes that the desktop client (app 2.19675) accepts the rows and columns given to ui.open but does not use them for pane size, so size is treated as whatever width the user drags.

The color and button findings point the same direction. Hex colors that read fine in the terminal, such as #7FD1A6, can wash out or become unreadable on a light desktop theme, so the author routes them through a small lookup table that maps familiar hex values to theme names. Buttons in the desktop app keep a fixed look — no color, shape or size control, and no HTML inside the pane — so the author's settled pattern is to draw the visuals with Svg and place plain, ready-made Buttons above or below the artwork, using plain: true and dimColor: true to keep them unobtrusive. An attempt to overlay a clickable Client on top of an Svg did not register clicks.

The grid problems come from the desktop's default opening, which the author describes as a narrow pane about 58 columns wide and 440px, next to the conversation. Layouts built for a wide screen collapsed there: charts shrank to thin bars, axis labels overlapped, and legends were cut off. The author's passing line is that text must not overlap or be cut off in that narrow pane, and that switching from a horizontal to a vertical arrangement once the artwork would fall under 60 columns, along with dropping legends from the back, was cleaner than truncating. The author also warns that the resolve table is filled with every component name, so the presence or absence of t.Svg will not tell you which surface you are on; Svg is available on desktop and Raster only in the terminal.