Find the thing that looks wrong, apply the fix, then go back to the page you were testing.Documentation Index
Fetch the complete documentation index at: https://docs.airglow.cc/llms.txt
Use this file to discover all available pages before exploring further.
| Case | Likely cause | Solution | Check |
|---|---|---|---|
| Airglow does not appear in Chrome extensions | Chrome has not loaded the unpacked extension folder. | Open chrome://extensions, turn on Developer Mode, click Load unpacked, and select Airglow-dev-kit/extension. | Airglow appears in the extension list and is enabled. |
| You cannot find the right folder | The wrong folder is selected during Load unpacked. | Select the extension folder inside Airglow-dev-kit, not the repo root. | Chrome accepts the folder without an error. |
| Local apps do not load | The local app server is not running. | In Airglow-dev-kit, run pnpm airglow dev again. | The terminal shows that the app server is running. |
| The app does not appear on Hacker News | The page was opened before the server or extension was ready. | Keep pnpm airglow dev running, reload the extension, then refresh news.ycombinator.com. | The app panel appears on the Hacker News page. |
| Summarize does nothing | The generated app has a runtime error or missing model/API setup. | Ask the coding agent to inspect the browser console and terminal output, then fix the app. | Clicking Summarize shows five short bullets. |
| The page still shows the old app | The browser tab or local app server still has old state. | Refresh the target page. If needed, stop and restart pnpm airglow dev. | The visible app matches the latest agent change. |