Problem 

Debugging Reactive screens can be difficult when developers need to understand the current state of local variables, client variables, input parameters, screen data, and browser storage.

How this suggestion can help 

A dedicated Reactive Debug Panel would give developers a centralized view of the screen state during runtime, reducing the need for temporary labels, console logs, or manual debugging workarounds.

Implementation example 

Add a debug panel available during preview/debug mode showing:

Current Screen: RequestDetail

Local Variables

Client Variables

Input Parameters

Data Actions

Local Storage

Session Storage

The panel could allow developers to inspect values in real time and optionally copy them as JSON.