Cannot Highlight Text In Terminal

[mergesort]

I'm not sure if it's just on my machine but the cursor position is always wrong when I try to highlight using the integrated terminal.

In this screenshot I was trying to copy http://localhost:4321, but the cursor is wildly off. This is true for everything I try to highlight in general, which is frustrating for when I want to copy text.

---

(Related nit but I would really love to be able to command click links in the terminal like I can in iTerm, but that doesn't seem to work in CodexMonitor's terminal.)

Thank you very much for the hard work! I really love how this is coming along I'm spending almost all my time in CodexMonitor these days.

[Dimillian]

@codex any idea?
Working good on my machine.
I would like to know when this could happen.

[Dimillian]

@mergesort does it do it all the time? On brand new terminal too?

[chatgpt-codex-connector]

Likely cause (when this happens)

From the codebase, the UI “interface scale” is implemented by applying a CSS transform: scale(...) to the root .app container (and only removed when using the default scale). This means any non‑100% UI scale uses a transform on the whole app, which can cause coordinate mismatches in canvas-like components such as xterm.js (selection/cursor offsets are a common symptom). This is wired via the --ui-scale CSS variable, which is set from the app settings and then used for the transform on .app. src/App.tsxL1738-L1755 src/styles/base.cssL297-L315

So when should you expect it?

• When the interface scale is not 100% (i.e., anything other than the default scale), because the transform is active and xterm selection math can drift under a scaled coordinate system. src/App.tsxL1738-L1755 src/styles/base.cssL297-L315
• It will not occur at the default scale because the transform is removed by the .ui-scale-default class. src/styles/base.cssL313-L315

Quick verification / workaround

• Reset the interface scale to 100% (default) and check if selection becomes accurate again. That should disable the transform entirely via the .ui-scale-default class, which avoids the scaled coordinate space. src/styles/base.cssL313-L315

---

Commands I ran while investigating

• rg -n "ui-scale" src/App.tsx
• nl -ba src/App.tsx | sed -n '1738,1765p'
• nl -ba src/styles/base.css | sed -n '290,330p'

If you want, I can prepare a code change that keeps UI scaling but avoids terminal selection offsets (likely by switching the scaling technique or isolating the terminal from the global transform).

View task →

[Dimillian]

@codex yes I could reproduce it, so now you know how to fix it

[chatgpt-codex-connector]

Summary

• Switched UI scaling to use CSS zoom with a transform fallback for engines that lack zoom, avoiding coordinate drift while preserving size compensation for non-default scales. src/styles/base.cssL297-L325

Testing

• ✅ npm run lint
• ✅ npm run typecheck

View task →

[Dimillian]

Trying: #217

[mergesort]

To answer your question yes, I can recreate it with a new terminal.

[Dimillian]

@codex: Switched UI scaling to use CSS zoom with a transform fallback for engines that lack zoom, avoiding coordinate drift while preserving size compensation for non-default scales. src/styles/base.cssL297-L325

This fix is not working, the scale is wrong + it scale the whole interface within the window.
Can you find another fix?

[chatgpt-codex-connector]

Summary

• Added a UI scale mode hook that probes actual CSS zoom support at runtime to choose between zoom and transform scaling. src/features/layout/hooks/useUiScaleMode.tsL1-L42
• Wired the UI scale mode class into the app layout and split scaling behavior into zoom/transform-specific CSS rules with default resets. src/App.tsxL1321-L1354 src/styles/base.cssL297-L329

Testing

• ✅ npm run lint
• ✅ npm run typecheck

Screenshot

• Not captured (Tauri app UI isn’t runnable in the browser container).

View task →

[Dimillian]

Fixed in the next release