---
title: Get started
description: Sign in to your openlaunch console, pair a device and choose the functions your agent can use. Developers can also run the bridge locally.
---

## Connect your first device

1. [Open your console](https://www.openlaunch.dev/console/) and continue with Google.
2. Choose **Devices → Add device**, then choose your board or **Custom device**. Your console creates a single-use enrollment that lasts 10 minutes.
3. Follow the [Pi installer](/docs/pi) or [Uno USB setup](/docs/uno-r4). The device appears in your console when it connects.
4. Open **Agent permission**, choose ChatGPT or Codex, select its functions and set an expiry. [Connect the agent](/docs/agents).

You can run a function yourself from the device card, or ask a linked agent to use an approved function. Inspect the action receipt for the result. To add your own hardware behavior, see [Build your own functions](/docs/functions).

## Run a local developer console

You need [Node 24+ and Git](/docs/resources). On macOS or Linux, run:

```sh
curl -fsSL https://www.openlaunch.dev/install.sh | bash
```

The installer downloads the source, builds the console, and starts the bridge. It does not flash a board or change cloud resources. You can [read the hosted script first](/install.sh). The [GitHub copy](https://raw.githubusercontent.com/pkyanam/openlaunch/f2bc0d937bd86d2efc8549dfa3ffbabc3c8aa6de/scripts/install.sh) is the backup; both are published from the same source commit.

Open **http://127.0.0.1:8788**. On macOS, your owner session key is already on the clipboard: paste it into the session field and select **Connect**. On Linux, copy the `token` value from `.cache/local/owner.json` in the installed checkout. Keep that file private. Your session key is a password for your console; never give it to an agent.

The default installation is `~/.local/share/openlaunch`. An existing checkout is reused without resetting your files. To stop the bridge, press **Ctrl-C**. To start it again:

```sh
cd ~/.local/share/openlaunch
npm run start:local
```

## Add your board

In the console, select **Uno R4 WiFi** or **Pi** and create an enrollment. Follow the [Uno guide](/docs/uno-r4) or [Pi guide](/docs/pi) to connect it within 10 minutes.

For a real board, the bridge needs a trusted HTTPS address the board can reach. Your Mac's loopback address only works on that Mac. See [network setup](/docs/troubleshooting#my-board-cannot-reach-the-bridge).

## Connect your agent

Follow [agent connections](/docs/agents). Then grant that agent **health** for your device in the console. Ask it to check the board's health and inspect the result. Add LED or matrix access when you want the Uno to use those capabilities.

A grant is a permission slip: it names the agent, device, allowed capability, and expiry. Pairing alone doesn't give an agent permission.

## Work on the source

Already cloned the repository? Run `npm run setup` from its root. The installer needs only Node and Git. Building or testing the Pi agent also needs [Go](/docs/resources); flashing an Uno needs [Arduino CLI](/docs/resources).

Use `npm run check` for shared API, permissions and protocol tests. `npm run test:e2e` runs a simulated device through the local bridge; it requires Go and does not operate physical hardware. Platform details are in the [Mac handoff](https://github.com/pkyanam/openlaunch/blob/main/docs/MAC-HANDOFF.md).