The AI operating system we actually ship in a browser tab

For months, “AI OS” meant a screenshot of fake windows or a cloud VM with a chat sidebar. We wanted the uncomfortable version: a real kernel, real files you own, and an agent that edits the system while you watch.

That is vibeOS. This post is the narrative companion to our guide The AI Operating System for Codex & ChatGPT Agents — same facts, more story. If you only want the SEO checklist and FAQs, start there.

Why “AI OS” broke in 2025

Hackathon pitch, 2024: give Claude a UI and a shell, let one prompt build front and back. Cool demo, zero comprehension from passers-by. Then a Microsoft livestream said “VibeOS,” GitHub SEO did its thing, and suddenly everyone was asking whether my repo was real or performance art (I wrote that up).

The useful lesson: people do not want another chat. They want a place the agent lives — with persistence, tools, and software that did not exist five minutes ago.

What we built instead of a thicker chat box

Open vibeos.sh/app. Under the menu bar:

1. v86 boots Linux (Alpine fast path, Debian when you need apt).
2. A desktop — windows, dock, terminal — mostly plain JS you can fork per file.
3. An agent loop with tools that touch disk, the VM, and the UI.
4. MCP so Codex, Claude Code, or Cursor can drive the same desktop with their model.

The browser is the hardware abstraction: WebSockets for the guest NIC, canvas for the VGA screen, and optionally the File System Access API when you connect a workspace folder for persistence. It is not magic; it is plumbing that took a year of traps documented in our CLAUDE.md war stories.

“Download” vs “just open it”

We still publish a Docker image for people who want the whole stack on localhost. But the main funnel is a URL. No installer, no “trust this binary.” Send someone /app and in thirty seconds they know if an AI OS is a gimmick for them.

Open source (MIT) matters here: you can read every tool schema, every kernel file, every ui module. The agent is not a black box on a proprietary desktop.

Codex & ChatGPT agents need an OS, not another panel

Codex in a chat thread cannot apt install, cannot fork your window chrome, cannot leave you a dock app you reopen Thursday. vibeOS gives it those verbs — or gives your MCP client those verbs while you keep coding in Cursor.

Pairing looks like:

claude mcp add vibeos -- npx vibeos-mcp --token <from-settings>

The token is root on that tab. We say that loudly in the UI because security by vibes is how you learn humility.

Not ChatGPT desktop, not a cloud PC

• ChatGPT desktop — great product, wrong layer. Not your forkable Linux, not your git workspace of generated apps.
• Cloud PC — someone else’s machine. vibeOS runs the heavy stuff in WASM; optionally you can point it at a folder on your disk (Chromium) when you want persistence.
• Fake OS UIs — pretty screenshots. vibeOS is uglier and more honest: run uname, read /proc, break the shell, fix it with edit_file.

Details and comparison tables live on the AI operating system guide.

What to do next

1. Open the desktop and ask for one small app.
2. Read Launching vibeOS 2.0 for the full stack essay.
3. Star github.com/caffeinum/vibeOS if you want this to exist in public.

The canonical reference for search and FAQs remains The AI Operating System for Codex & ChatGPT Agents.