VibeAI Docs
VibeAI OS

Getting Started

What VibeAI OS looks like day one, and how to install it.

VibeAI OS is a self-hosted AI operating system: agents with persistent memory, document-grounded projects, cost-managed model access, and channels (web, Telegram, voice, CLI) — all on a server you (or we) control. Most of what you’ll do day to day happens in the web dashboard, not the shell.

Logging in

After install, the dashboard is at https://aios.<yourdomain> (server installs) or http://localhost:9200 (local installs) — sign in with the admin user and the password you chose during provisioning.

The sidebar, section by section

The left sidebar is grouped into five sections. Every page underneath is backed by a real API — nothing in the dashboard is a mockup.

Operate

Dashboard, Chat, Console, Vibe Code, Projects, Sessions — the surfaces you use to actually talk to and work with agents.

Intelligence

Analytics, Models, Reviews — spend, model selection, and the self-review log.

Automate

Cron, Skills, Plugins — scheduled jobs and reusable capabilities.

Connect

Channels, MCP, Webhooks, Access — how the outside world reaches an agent, and who’s allowed to.

System

Clients, Agents, Config, Keys, System, Logs, Docs — fleet and box-level administration.

Operate

  • Dashboard — the landing page: gateway state, stat tiles, recent sessions, and a query bar wired to live agent chat.
  • Chat & Console — message-bubble chat or a terminal-style REPL, both against the same agent socket.
  • Vibe Code — the full coding workstation: real Claude Code CLI sessions, multiple tabs, task tracking, project management, skill/agent creation.
  • Projects — document folders agents retrieve from and cite when answering.
  • Sessions — every conversation transcript, across every channel.

Intelligence

  • Analytics & Budgets — spend ledger, per-model breakdowns, and opt-in budget enforcement.
  • Models — switch the active provider/model with a click instead of a config edit.
  • Reviews — the meta-reviewer’s cold-context corrections log.

Automate

  • Cron — scheduled agent jobs.
  • Skills & Hooks — reusable verified skills and lifecycle hooks.
  • Plugins — installable dashboard/agent extensions.

Connect

  • Channels — per-agent Telegram bots and other message channels.
  • MCP — external MCP servers an agent can call tools on.
  • Webhooks — inbound HTTP triggers into an agent.
  • Access — auth, remote access, and per-surface gates.

System

  • Clients — fleet/tenant view (mothership installs only).
  • Agents — agent profiles, gateway state, credentials.
  • Config — the raw config.yaml editor.
  • Keys — .env provider API keys.
  • System — CPU/memory/disk and service state.
  • Logs — live tail of dashboard/gateway logs.
  • Docs — this manual.
Tip

Every nav link lands on real, working data — if a page ever looks bare, it’s because that feature genuinely has nothing configured yet (no projects created, no cron jobs scheduled), not because it’s a stub.

Installing

The dashboard above is what you get after running one of these installers.

Server install (Ubuntu)

On a bare Ubuntu server, from an unpacked release (or repo checkout):

APEX_DOMAIN=yourdomain.com ADMIN_PASSWORD=choose-one \
  ./deploy/provision.sh --with-chroma
Info

This is idempotent — re-running never overwrites existing config, credentials, or data. It installs packages, binaries, systemd units, nginx sites (aios.<apex> dashboard, vibe-ui.<apex> panel), creates the gateway password, and scaffolds /root/.aios.

Local install (your own machine, incl. macOS)

For running VibeAI OS on a laptop/workstation instead of a shared server — no nginx, no auth proxy, no license gate, just your own account:

git clone <this repo> && cd vibeai-os
./deploy/provision-macos.sh --dry-run   # see the plan first, changes nothing
./deploy/provision-macos.sh             # builds aios + aios-dashboard from
                                         # source and installs to ~/.local/bin

Installs Rust via rustup if missing, builds native binaries for your machine’s architecture (no cross-compilation), and scaffolds ~/.aios. Add --with-launchd to have the dashboard/gateway start at login and restart on crash; without it, run them manually (aios chat, aios-dashboard --port 9200). --skip-build reuses an existing release build for a quick re-provision.

First five minutes after provisioning

Run the setup wizard

aios setup — walks through provider selection (all of DeepSeek, Anthropic, OpenAI, Gemini, OpenRouter, Groq, Mistral, xAI, Ollama, or a custom endpoint), model choice, and your API key, and actually writes them to /root/.aios/config.yaml and .env. aios setup -y accepts defaults non-interactively (DeepSeek v4 Flash, no key prompt — add one to .env yourself after).

Restart the services

systemctl restart aios-dashboard aios-gateway (server installs only — a local --with-launchd install restarts itself; without launchd, just re-run the binary).

Log in

https://aios.<apex> (user admin, your ADMIN_PASSWORD) — server installs only.

Smoke-test

aios -p "hello" from the shell — you should get an answer streamed through the full harness.

What a running install looks like on disk

PieceWhat it isWhere
aiosCLI + agent runtime + gateway/usr/local/bin/aios
aios-dashboardweb API + this UI:9200, behind the auth proxy
aios-gatewayTelegram/channel daemonsystemd aios-gateway[@profile]
AIOS homeALL state (config, sessions, memory, projects)/root/.aios
Auth proxieslogin gates per subdomainvibe-ui-auth, aios-dashboard-auth

Verifying an install

./deploy/e2e.sh yourdomain.com runs the 18-check acceptance suite — services, APIs, gateways, a real agent turn, memory persistence, budget enforcement, and the project lifecycle. Everything green = healthy box.