What is computer use in vibeOS?

The agent can read the desktop, run commands in the Linux guest, edit files, create dock apps, and use the terminal and browser panes — via built-in chat or vibeos-mcp from your IDE.

Can Cursor or Claude Code control vibeOS?

Yes. Pair vibeos-mcp using the token and relay URL from Settings › Capabilities. Your MCP client keeps the model; vibeOS is the environment it operates.

Does vibeOS replace ChatGPT desktop for computer use?

No. ChatGPT desktop is OpenAI's app. vibeOS is an open MIT desktop you can use with Codex login, API keys, or external MCP agents — vibeOS is the computer, not the chat product.

Computer use for AI agents: vibeOS as the desktop layer

When people talk about computer use for AI agents, they usually mean giving a model like Codex, ChatGPT, Claude, or Cursor access to a screen, a shell, and a filesystem. Often that means using a VM hosted by the AI company, or wiring up a fragile browser automation script yourself.

vibeOS (vibeos.sh) is an open agent desktop that takes a different approach. It gives you a Linux environment in the browser (or in Docker on your local network) where the agent can use a set of tools, while you stay in control of the "brain": you can use your own API key, your Codex login, or an MCP client like Cursor.

This is Aleks Bykhun's vibeOS, an MIT project at github.com/caffeinum/vibeOS. It's not related to Kaan Senol's Raspberry Pi OS, it's not a generic "AI PC" subscription, and it's not just a chat wrapper.

Open the agent desktop →

What vibeOS gives an agent

Observe — read_desktop (to see the windows, dock, and VM state, as well as an optional JPEG of the VGA screen), list_files, search_file.
Act — vm_exec, edit_file, create_app, reload_ui / reload_os, browser and terminal panes inside the guest OS.
Persist (optional) — there can be a workspace folder on disk for apps and chat, and VM snapshots in the workspace.

The built-in chat interface uses the same tool loop. You can also bring your own agent using vibeos-mcp: go to Settings › Capabilities in the desktop and it will print a pairing command, and the relay will pair your IDE agent with the tab.

Codex & ChatGPT vs Cursor & Claude Code

You use	How vibeOS fits
Codex / ChatGPT	Log in on vibeos.sh/app. The built-in agent drives the desktop.
Cursor / Claude Code	Run `npx vibeos-mcp --token …` (and `--relay` when self-hosting). Your client keeps control of the model, and vibeOS is the hands + monitor.

Positioning detail: The AI operating system for Codex & ChatGPT agents.

Browser OS vs container workshop

Browser (/app) — zero install. You can run a WASM Linux OS. Best for trying computer-use flows in a tab. See Browser OS.
Docker — a self-contained server + disks on localhost. Pair MCP with the relay URL shown in the pane. The security risks and available Docker tags are documented in the main README — read it before running release candidates.

Setup steps: How to use vibeOS.

What computer use is not

Not replacing your IDE — vibeOS is the environment agents operate in, often alongside your editor.
Not unlimited host access in the web build — guest networking and browser sandbox boundaries apply unless you choose a self-hosted setup and understand its network policy.
Not a hosted multi-tenant cloud PC — each person uses one tab (or one container). There's no shared "agent farm" on vibeos.sh.

Get started

Open vibeos.sh/app and wait for the VM to load.
Connect a model or pair MCP from your agent client.
Ask the agent to create a dock app, run a command in the VM, or read the screen — then iterate.

For FAQs and comparisons to ChatGPT desktop, see the pillar guide: AI operating system.

Open vibeOS →