Installation & Setup
Get Glider running locally, with the database, ports and optional hardware in place.
Stream Deck, agent CLIs and LAN access.
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.