Feature request: Manual keyboard layout selection for remote sessions

[garfield50]

Hello,

Could you add a manual keyboard layout selector to Breeze remote sessions?

Currently, French AZERTY keyboards are interpreted as QWERTY, which causes incorrect key mapping during remote control.

A session-level option allowing the technician to manually select the keyboard layout, such as AZERTY, QWERTY or QWERTZ, would solve the issue.

Thank you.

[ToddHebebrand]

Confirmed — and I've traced exactly why. There is currently no layout handling anywhere in the pipeline, so AZERTY (and QWERTZ) viewers get QWERTY behavior end-to-end:

• The viewer maps keystrokes preferring KeyboardEvent.code — a physical position name that is always US-QWERTY-labeled regardless of your actual layout (apps/viewer/src/lib/keymap.ts) — and sends that over the input channel.
• On the remote side, the Windows and macOS injectors use hardcoded QWERTY-position tables (charToVK in agent/internal/remote/desktop/input_windows.go; the macOS keycode table is even commented "QWERTY layout keycodes"). Only the Linux injector resolves keysyms against the live X keymap, and that fixes just the injection half.

So your azerty → qwerty observation is the textbook symptom: position goes in, position comes out, layouts never consulted on either end.

The fix shape is what you proposed: a session-level layout selector (AZERTY/QWERTY/QWERTZ to start) in the viewer toolbar — next to the existing Cmd/Ctrl swap toggle — sent as a new session-control message (the channel already carries set_bitrate / switch_monitor etc.), with the agent's key tables made layout-aware. Automatic detection from the viewer's KeyboardEvent.key values is plausible as a later refinement, but the manual selector is the reliable v1.

Accepted; keeping this discussion as the tracker until an implementation issue is opened.