### System details

Ryzen 5600x with 3060 12 gb varient and 32 gb of ram 

### What's wrong?

I am experiencing an intermittent mouse click/input offset issue in the Omarchy status bar.

The issue primarily affects the modules on the right side of the status bar, including:

- Agents
- Dropbox
- Tailscale
- Speaker / Audio
- System Tray

The visual rendering of these modules appears correct, but their actual mouse click/input regions can become slightly offset from their visible positions.

### What I mean by "click offset"

When the issue occurs, an icon/button can be visually displayed at one position, but clicking directly on the visible element does not activate it.

Instead, the actual clickable area may be shifted slightly above or below the rendered element.

For example:

```text
     VISUAL POSITION
          ↓
      [ ICON ]

          ↑
     ACTUAL HIT AREA

The offset is relatively small, but noticeable enough that the mouse sometimes needs to be moved slightly away from the visible icon in order to trigger the expected action.

The important point is that this appears to be a mismatch between the rendered widget geometry and its actual mouse/input hit-testing geometry.

Observed behavior
The issue is intermittent.
It primarily affects the right-side status bar modules.
The status bar can initially work correctly.
The problem can appear later during normal usage.
The visual position of the affected elements does not necessarily look wrong.
The problem is specifically noticeable when interacting with the affected modules using the mouse.
Restarting the Omarchy shell has previously caused the issue to disappear.
After the shell restart, the click targets can become correctly aligned with the visual elements again.
The issue may potentially reappear later.

I am not claiming that any particular application causes the issue. I noticed it during normal use after installing and using the system today, but I do not have evidence that a specific application is responsible.

Expected behavior

The clickable/input region of every status bar module should remain aligned with its rendered position.

For example:

      [ ICON ]
          ↑
       CLICK

Clicking directly on the visible icon should activate that icon.

Actual behavior

When the issue occurs, the rendered position and input position can appear to diverge:

      [ ICON ]
           

          ↑
      CLICK HERE

This makes the status bar feel as if its mouse hitboxes have moved relative to the UI.

Additional observation

Restarting the Omarchy shell temporarily resolves the problem.

This is particularly interesting because it suggests that the issue may be related to runtime layout/input geometry, cached coordinates, or a layout/input state that becomes incorrect during the session.

The shell restart appears to rebuild/reset the relevant UI state and restore correct click alignment.

Questions / investigation

I would like to understand whether this could be related to:

Quickshell widget geometry
status bar layout/re-layout
parent/child coordinate mapping
stale or cached widget positions
mouse hit-testing
input regions
layer-shell geometry
Wayland layer/input handling
Hyprland layer-shell interaction
monitor scaling or coordinate conversion
dynamic changes in the right-side status bar
System Tray layout changes
any shared/global click-target calculation used by the right-side modules

In particular, I would be interested in knowing whether the visual geometry and the input/hit-test geometry can become out of sync after a runtime layout change.

Why is this intermittent?

The issue does not appear to be present continuously.

The status bar can work correctly and later enter a state where the click targets become offset.

A shell restart restores the expected behavior.

This makes me wonder whether there is a runtime state, re-layout, geometry recalculation, or coordinate-mapping condition that can cause the mismatch.

Why might this affect some systems but not others?

I do not know whether this is specific to my system or whether it is a less common state-dependent issue.

If this is not widely reproducible, potentially relevant environmental factors could include:

monitor resolution
monitor refresh rate
scaling/fractional scaling
NVIDIA GPU/driver
Hyprland state
Quickshell runtime state
single/multi-monitor configuration
dynamic status bar module state
System Tray contents
timing of layout recalculation
Wayland/layer-shell state

I am not suggesting that any of these are definitely responsible. They may simply be useful areas to investigate.

Environment
Omarchy 4.0.3
Fresh Omarchy installation
Hyprland
Quickshell
NVIDIA GPU
Default Omarchy status bar
What I would like investigated

I would appreciate an investigation into the complete path from:

Rendered widget
      ↓
Widget geometry
      ↓
Parent / Row / layout geometry
      ↓
Layer-shell surface geometry
      ↓
Input / hit-test region
      ↓
Mouse coordinate mapping
      ↓
Click-target selection

The main goal is to determine whether there is a situation where the rendered position of a right-side status bar module differs from the position used for mouse hit-testing.

If possible, it would also be useful to determine:

What exactly becomes offset.
Where the incorrect geometry originates.
How that incorrect geometry reaches the input/hit-testing logic.
Why the visual rendering can remain correct.
Why the right-side modules are particularly affected.
Why restarting the Omarchy shell restores correct behavior.
Whether this is related to Quickshell, Omarchy's status bar implementation, Hyprland/layer-shell, or an interaction between them.
Whether there is a specific runtime condition that triggers the problem.

I have not made any custom modifications to the Omarchy status bar to intentionally produce this behavior.

The issue is intermittent, so I am providing this report primarily to document the behavior and help identify the underlying cause.