Open SDK beta quick start

From GitHub checkout to your first browser-native SDK app.

Airglow's beta is open for SDK builders. Clone the dev kit, load the ready extension, allow user scripts, prompt an agent, and verify the result on a real page.

Open GitHub Read the SDK quickstart

Install once

Clone the dev kit, then load the included extension.

This is the only setup block: clone from GitHub, start the local SDK server, and point Chrome at the repo's `extension/` folder.

Terminal

git clone https://github.com/Airglow-up/Airglow-dev-kit.git
cd Airglow-dev-kit
pnpm install
pnpm airglow dev

Chrome

1. Open `chrome://extensions`.
2. Enable Developer mode.
3. Load unpacked → select `Airglow-dev-kit/extension`.
4. Details → enable Allow User Scripts.

Build loop

After install, make one thing visible.

Do not repeat setup here. Use this loop to prompt, verify, and tighten the first app before expanding it.

Prompt one visible app

Ask your coding agent for one userscript-backed app, one target page, and one obvious visual result. Keep the scope small until it loads cleanly.

Verify in the browser

Open the target site, confirm the Airglow UI appears, and check the dashboard/logs before adding more behavior.

Keep the first loop shippable

Use `airglow.*` SDK APIs for logging, storage, fetch, and RPC. Keep page code visible and server-side secrets out of the browser.

Example agent prompt

Give the agent a page, one app, and a visible success condition.

Prompt

Create a small Airglow SDK app called hn-page-brief.

Goal:
- Run on https://news.ycombinator.com/*
- Read the top 10 story titles from the page
- Add a compact Airglow panel at the top of the page
- Show the titles and a "summarize" button

Constraints:
- Use a userscript first; do not call chrome.* directly
- Use only the global airglow.* SDK for storage/logging/fetch/RPC
- Keep secrets server-side if you add an API call
- Make the first version easy to verify visually

What you should get

A small app you can see and inspect.

`airglow-apps/hn-page-brief/manifest.json` declares the app and page matches.
A userscript runs on Hacker News, reads titles, and renders a compact panel.
The app uses `airglow.log` / `airglow.storage` instead of direct extension APIs.
The Airglow dashboard/logs show whether the app loaded cleanly.

GIF and screenshot slots

Drop short animations here before launch.

Keep each animation focused on one motion: load the extension, enable the permission, then show prompt-to-result.

GIF slot 01

Load `extension/` in Chrome

Add a short animation of Chrome Developer mode → Load unpacked → select the `extension/` folder.

GIF slot 02

Enable Allow User Scripts

Show the extension details screen and the exact toggle that must be enabled for userscripts.

GIF slot 03

Prompt → page result

Show the agent prompt, generated app files, `pnpm airglow dev`, and the visible result on the target page.

Need the full SDK contract?

Use the SDK docs for API shape, app anatomy, permissions, server RPC, and debugging after the first visible app is running.

Open SDK quickstart