> ## 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.

# Advanced settings

> Configure local display, performance, and debugging options on the device

BRICKS Foundation includes advanced settings that you configure locally on each device. For general device settings like application binding, display name, and device groups, use [BRICKS Controller](/controller/devices).

## FPS monitor

Enable the FPS monitor to display a real-time frame rate counter on screen. This helps identify performance issues in your applications.

## External display

BRICKS Foundation detects external displays connected to your device. When an external display is detected, you can choose to:

* **Mirror** the primary display content
* **Extend** to show different content on each display

<Info>
  External display support varies by platform. Desktop platforms support multiple monitors. Mobile devices support AirPlay (iOS) and screen casting (Android).
</Info>

## Local debugging

Local debugging lets you inspect and drive the running application from your computer over the local network. It is a **Preview** feature and is **on by default** on BRICKS Foundation 2.25 and later — the DevTools server starts at boot with no setup.

Toggle **Enable local debugging** to turn the server on or off entirely. While it is on, three sub-toggles control which protocols the server exposes, all on by default:

| Setting                                   | What it controls                                                       |
| ----------------------------------------- | ---------------------------------------------------------------------- |
| **Enable Chrome DevTools Protocol (CDP)** | The CDP endpoint used by Chrome DevTools and CDP automation tools      |
| **Enable Model Context Protocol (MCP)**   | The MCP endpoint for AI agent integration                              |
| **Enable LAN Discovery**                  | Whether the device answers `bricks devtools scan` on the local network |

Set an optional **Passcode** to require a passcode for access — the field is blank by default with the placeholder "Set a passcode to enable passcode access". Leave it blank to rely on workspace-token access only. **Expose passcode to chrome://inspect** (off by default) embeds the configured passcode into the public `/json` discovery URLs so Chrome can connect without prompting.

See [local debugging](/foundation/local-debugging) for connection instructions. For remote inspection through BRICKS Controller, see [remote debugging](/foundation/remote-debug).

## Memory management

BRICKS Foundation monitors memory usage and can automatically restart the application when memory exceeds a threshold. Configure the auto-restart memory limit in settings to prevent out-of-memory crashes on resource-constrained devices.

## AI API keys

Configure API keys for on-device AI capabilities:

| Provider          | Description                                    |
| ----------------- | ---------------------------------------------- |
| **OpenAI**        | GPT models for text generation and analysis    |
| **Anthropic**     | Claude models for text generation and analysis |
| **Google Gemini** | Gemini models for text generation and analysis |

API keys are stored locally on the device and used for AI features within your applications.

## Local server mode

Enable local server mode to serve applications from a local development server instead of the [BRICKS](https://bricks.tools) cloud. This is useful for local development and testing.

## Data Bank sandbox mode

Enable sandbox mode to isolate Data Bank data on the device. In sandbox mode, data changes are not synced to the server, allowing safe testing without affecting production data.