VibeOS starter kit

Each example covers one part of window.vos and shows every call it makes, what came back and the errors you can get. Copy the helpers at the bottom of each page into your own app.

Examples · one feature each

📁

FilesWrite, read, list, move and delete files, plus a live view of everything you saved.vos.fs · works right away

✨

AICheck access, ask questions, chat with memory and get JSON back.vos.ai · needs a developer key

🌐

NetworkCall web APIs without CORS problems. Includes GET, POST, 404s and blocked URLs.vos.net · needs a developer key

🛡️

PermissionsSee what vibe.json allows and blocks, and how to check before you call.vibe.json · works right away

Sample apps · complete apps to learn from

✅

To-Do ListLists, due dates and priorities saved as one JSON file.Files

🗂️

File BrowserBrowse, edit, upload and download files in Documents, including those the examples saved.Files

💬

AI ChatSaved conversations and clear messages for plan and credit problems.Files + AI

📰

News ReaderRSS and Atom feeds with unread counts and a reading view.Files + Network

Build your own

Start in my-app/. It has a blank index.html with the dev script already in place, and a vibe.json for its name and permissions. Open it
Add a developer key for AI and network. Create one in the Dev Portal → Developer SDK, then click the VibeOS dev badge in the corner and paste it. Files work without a key.
Check your files any time in the badge. It lists every file in the dev home folder, which all these pages share like apps do in VibeOS.
Package it and upload the .vibe file in the Dev Portal → Submit App:
```
cd my-app && node ../vibeos-pack.mjs index.html vibe.json
```

Double-clicking works for everything here. In my-app, the browser can't read vibe.json from a double-clicked page, so permissions are only checked when you serve the folder (npx serve .). The examples keep their manifest inside the page, so they're checked either way.