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.

curl -fsSL https://avibe.bot/install.sh | bash && vibe

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 that goes where you do

Chat with your agent right in the browser — or install the Workbench as a desktop or mobile app and get a push notification the moment a job needs you. Same agent, same sessions, at your desk or on the move.

🧠 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. Ask in plain language; it composes the commands.

🧩 Skills across every agent

Reusable skills — your conventions, your workflows — managed in one place and shared across Claude Code, Codex, and OpenCode. Set them up once; every agent you run inherits them.

📱 In your pocket

Your machine runs the work; you don't have to sit in front of it. Run vibe remote and your local Workbench becomes reachable from any browser on Earth — through a secure avibe.bot tunnel — with no VPN, no port forwarding, and no public webhooks pointed at your laptop.

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.

Why Avibe is different

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

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.

Talk to it like a colleague

Ask in plain language and the Harness composes the commands behind the scenes:

• "Watch this PR and come back when there's actionable review feedback."
• "Run the deployment check every weekday morning and post the summary here."
• "Start a separate investigation session for this incident, but report the conclusion to this channel."
• "If CI fails, summarize the logs; if it passes, tell me whether the PR is mergeable."

Switch agents mid-conversation — just prefix your message:

Plan: design a new caching layer for the API

Route per project — different work, different agent:

frontend   → OpenCode    (fast iteration)
backend    → Claude Code  (complex logic)
prototypes → Codex        (quick experiments)

Meet Vibey

Lives in your Workbench and your chat apps. Reads the room. Picks up where you left off. Asks the right question when it's unsure. Goes quiet when you're heads-down. Ships at 2am because that's when the vibe hits — then leaves a note about what it touched.

Avibe is the home your agent lives in. Vibey is the colleague who lives there.

Forgets no