avibe

Avibe

The local-first Agent OS — your AI partner lives on your own machine.

Own the agent. Reach it from anywhere. Never get locked in.

Docs · English · 中文

Drives

Reach it from

---

Your AI agent is brilliant — and stuck

Claude Code, Codex, OpenCode are incredible. But:

• 🖥️ Trapped on one machine. Your agent lives in a terminal. Close the laptop and it stops.
• 📵 Out of reach. Away from your desk, you can't see what it's doing — let alone steer it.
• 🔒 Locked in. Every tool wants to be the whole stack: its app, its cloud, its subscription, your code uploaded to someone else's box.

Avibe flips that

One command turns your own machine into the home your AI partner lives in. You drive the official Claude Code, Codex, and OpenCode — from a browser or any chat app — while your code and keys stay on your machine, and avibe.bot never sees your data.

bash -o pipefail -c 'curl -fsSL https://avibe.bot/install.sh | bash -s -- --launch'

The browser opens, you follow a short wizard, and your machine becomes an Agent OS you can reach from anywhere.

Open source — read the install script first if you like. The short URL is a 307 redirect to that file.

We recommend WSL on Windows for the best compatibility — see Run Avibe with WSL from scratch. It covers where to install WSL, which terminal to use, where to run the install command, and how to open the Web UI.

💚 Built with Avibe. This project was developed end-to-end using Avibe itself — steering Claude Code, Codex, and OpenCode from the browser and from my phone, picking up seamlessly whether I was at my desk or not. The deeper in I got, the faster it went. — @alex_metacraft

---

What you get

💬 A Workbench, not another chat box

Chat, inspect files, edit code, and run terminal commands in one windowed workspace. Built-in apps and the Show Pages your agent creates open side by side, so the browser feels like an Agent OS instead of a settings dashboard.

🧠 Its own timeline — the Agent Harness

Most AI tools only act when you type. Avibe gives your agent durable primitives — run, schedule, watch, and inspect — so it can start work, wait for the right moment, run in the background, and come back with results. Task and watch details expose their trigger, Agent and session binding, delivery configuration, and run history; standalone definitions can intentionally omit a conversation delivery target.

🤖 Bring the agents you already trust

Run the official Claude Code, Codex, and OpenCode CLIs behind one Agent registry. Choose models and reasoning per Agent, route projects to the right specialist, and keep reusable Skills shared across backends.

Open Runs to see that collaboration as a graph: who started each background Session, where it reports back, and the execution history behind every node.

🎨 Show Pages — point, comment, and iterate

When a picture beats a paragraph, your agent hands you a live web page — a flowchart, dashboard, diff, report, or small app. Comment on an element or screenshot, and the agent can rework the page or answer exactly where you pointed.

In Chat, click Visualize to switch the current session to its Show Page. Hover the button to open the page in a new app window or browser tab. You can also drag the button downward and release to place a new app window at the pointer, or drop it on Apps to pin that Show Page to the Dock.

See Show Pages for synchronous API timeout behavior and guidance for longer background refreshes.

🔐 Vaults — secret values stay out of Vault responses

Add a Standard secret once and approve Agent requests from the browser. Avibe's Vault responses never include the secret value; commands receiving it must still avoid printing it. Protected, passkey-gated custody remains pre-launch until the sandbox integrity gate is enforced.

🌐 Browser and messaging are equal surfaces

Use the Workbench when you want windows and rich interaction; use Slack, Discord, Telegram, WeChat, or Lark / Feishu when chat is the fastest route. They reach the same Agents and sessions.

📱 In your pocket

Your machine runs the work; you don't have to sit in front of it. Install the Workbench as a desktop or mobile app, use built-in voice-to-text, and get a push notification when a job needs you. Run vibe remote and the same local Workbench becomes reachable from any browser through a secure avibe.bot tunnel — no VPN or port forwarding.

You're on a plane, at a café, on a borrowed laptop. The agent pings that a job needs you. Open the link, steer it, walk away again.

• 🌍 Your own you-app.avibe.bot — 30-second sign-in, your slug for life
• 🔒 Fail-closed at every join — auth, routing, and host checks default to "deny"
• 📱 Mobile-aware UI — thumb-friendly, built for borrowed screens

Your data plane stays on your machine; avibe.bot only carries the control-plane handshake.

Plus — per-channel Agent routing · resumable sessions (thread = session) · interactive prompts · voice-to-text · file attachments · push and completion notifications.

---

Why Avibe is different

Local-first, and yours	Your AI partner, its execution, your keys, and your data stay on your machine. avibe.bot only issues identity and a secure tunnel — it never proxies your data.
One substrate, every first-party agent	Drive the official Claude Code, Codex, and OpenCode. Bring your own subscription or keys, switch per task, and never get locked into one vendor's silo.
Browser and chat, both first-class	Operate from the browser Workbench, or from Slack, Discord, Telegram, WeChat, and Lark / Feishu. Same agent, same sessions.
No middleman	No extra reasoning loop sits between you and your agent. Tokens go straight to the agent you chose.

---

How it works

┌──────────────┐            ┌──────────────┐            ┌──────────────┐
│     You       │  browser   │              │   stdio    │  Claude Code  │
│  (anywhere)   │   Slack    │    Avibe      │ ─────────▶ │  OpenCode     │
│               │  Discord   │ (your machine)│ ◀───────── │  Codex        │
│               │  Telegram  │              │            │               │
│               │  WeChat    │              │            │               │
│               │  Lark      │              │            │               │
└──────────────┘            └──────────────┘            └──────────────┘

1. You type — in the browser or a chat app: "Add dark mode to the settings page."
2. Avibe routes to your configured agent, in the right project.
3. The agent reads your local codebase, writes code, and streams back.
4. You review in the same surface, iterate in the thread, and resume later from anywhere.

Your code stays on your machine. Avibe runs locally and connects out via Slack Socket Mode, Discord Gateway, Telegram long-polling, WeChat polling, or Lark WebSocket — no public inbound ports for normal chat control. Prompts go only to the AI provider you choose.

---

Avibe vs OpenClaw

	Avibe	OpenClaw
Setup	One command + web wizard. Done in minutes.	Gateway + channels + JSON config. Expect an afternoon.
Security	Local-first. Socket Mode / WebSocket only. No public inbound ports, minimal attack surface.	Gateway exposes ports. More moving parts, more surface.
Token cost	No extra reasoning loop in between. Tokens go straight to your chosen agent.	Every message carries a long persona/orchestration context. Tokens burn on overhead before your task starts.
Lock-in	Drives the official agent CLIs; bring your own keys; switch per task.	Tied to its own assistant loop.

OpenClaw is an always-on personal assistant — great for casual chat, expensive for real work. Avibe is a local-first Agent OS for the agents you already trust: the agent stays itself, your data stays local, and the colleague experience comes from putting the agent into the flow where your work already happens.

---

FAQ

Local-first here means your code, data, and execution stay on your machine — not the model weights. Avibe drives the agent you configure (Claude Code, Codex, OpenCode); OpenCode can point at local or OpenAI-compatible endpoints if you want inference local too.