# Installation & Setup: Hardware & extras

> Stream Deck, agent CLIs and LAN access.

Glider documentation · Getting Started · Web page: https://cgglider.com/docs/installation/hardware/

Sections of this page: [Requirements](https://cgglider.com/docs/installation.md) · [Run locally](https://cgglider.com/docs/installation/run-locally.md) · [Environment & ports](https://cgglider.com/docs/installation/environment.md) · [Hardware & extras](https://cgglider.com/docs/installation/hardware.md)

## Stream Deck

The driver runs inside the Next.js server process, because the panel is on the same desk as the machine. It no-ops when no deck is attached. Its native modules — @elgato-stream-deck/node, node-hid and @napi-rs/canvas for key rendering — must stay in serverExternalPackages: bundling them breaks the native binding lookup.

## Agent CLIs

The AI tab runs Claude Code, Cursor Agent or Codex installed on this machine, using your own CLI sign-in. They reach the page only through Glider's MCP server at /api/mcp. You can also connect those tools yourself from your IDE.

## LAN access

Dev mode allows cross-origin requests from 10.40.40.* so another machine on the LAN can load /editor. Without that allowance the page loads but nothing is interactive, because the dev-only HMR endpoints are blocked.

> **File serving is locked down:** Page file URLs are served with nosniff, SAMEORIGIN and a restrictive Content-Security-Policy — no scripts, no external loads. Uploaded assets cannot execute.