> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bricks.tools/llms.txt
> Use this file to discover all available pages before exploring further.

# Remote debugging

> Inspect application properties remotely via BRICKS Controller

Remote debugging lets you inspect application properties in real time from [BRICKS Controller](/controller) without needing local network access to the device. This is useful for devices deployed in the field, at client sites, or in locations you cannot physically access.

## Start a remote debug session

<Steps>
  <Step title="Open the device in BRICKS Controller">
    Go to [BRICKS Controller](/controller/devices) and click on the device you want to debug.
  </Step>

  <Step title="Start remote debug">
    Click **Remote Debug** on the device detail page. The controller connects to the device and retrieves the list of available properties.
  </Step>

  <Step title="Select properties to monitor">
    Choose which properties you want to inspect. Only selected properties are streamed to reduce data volume.
  </Step>
</Steps>

<Info>
  The device must be online and connected to the BRICKS server for remote debugging to work. This feature may not be available on all workspace plans.
</Info>

## What you can inspect

The remote debug session displays real-time property values from the running application:

* **Data node values** — Current state of data nodes
* **Generator properties** — Configuration and outlet values
* **Brick properties** — UI component settings and bindings

### Filtering

Use the filter options to narrow down the property list:

* **Search by name** — Filter properties by keyword
* **Hide auto-generated** — Show only user-defined properties
* **Hide commands** — Filter out command-type nodes

You can copy property values to the clipboard for further analysis.

## Remote debugging vs local debugging

| Feature              | Local debugging                               | Remote debugging                        |
| -------------------- | --------------------------------------------- | --------------------------------------- |
| **Network**          | Same local network required                   | Works over the internet                 |
| **What you inspect** | Full DOM, JavaScript, network, performance    | Application property values             |
| **Setup**            | Enable DevTools on device, connect via Chrome | Click Remote Debug in BRICKS Controller |
| **Best for**         | Development and deep debugging                | Monitoring field-deployed devices       |

For full DOM inspection, JavaScript debugging, and performance profiling, use [local debugging](/foundation/local-debugging) on the same network. Use remote debugging when you need to check property values on devices you cannot access locally.

## Next steps

<CardGroup cols={2}>
  <Card title="Local debugging" icon="laptop-code" href="/foundation/local-debugging">
    Connect Chrome DevTools directly for full debugging capabilities.
  </Card>

  <Card title="Activity log monitoring" icon="chart-line" href="/foundation/activity-log">
    Monitor device events and application behavior over time.
  </Card>
</CardGroup>