Own the agent. Reach it from anywhere. Never get locked in.
Drives 
Reach it from 
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.
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 && vibeThe 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.
On Windows?
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
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.
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.
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.
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.
| 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. |
Coding is the first strong workload — not the product boundary.
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ You │ browser │ │ stdio │ Claude Code │
│ (anywhere) │ Slack │ Avibe │ ─────────▶ │ OpenCode │
│ │ Discord │ (your machine)│ ◀───────── │ Codex │
│ │ Telegram │ │ │ │
│ │ WeChat │ │ │ │
│ │ Lark │ │ │ │
└──────────────┘ └──────────────┘ └──────────────┘
- You type — in the browser or a chat app: "Add dark mode to the settings page."
- Avibe routes to your configured agent, in the right project.
- The agent reads your local codebase, writes code, and streams back.
- 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 | 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.
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)
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 nothing. Holds opinions. Says thanks when you fix its bugs.
vibe # Start Avibe and open the Workbench
vibe status # Check service and configuration status
vibe stop # Stop the local service
vibe doctor # Diagnose common setup issues
vibe remote # Reach your Workbench from any device via avibe.bot
vibe agent # Run and manage Avibe agents
vibe task # Schedule time-based work (cron / one-off)
vibe watch # Wait on a condition, then act
vibe runs # Inspect agent run history| In chat | What it does |
|---|---|
| Mention the bot | Start a task or ask a question |
| Reply in thread | Continue the same agent session |
/stop |
Stop the current session |
Full references: Commands · CLI
You need at least one coding agent installed:
OpenCode (recommended)
curl -fsSL https://opencode.ai/install | bashAdd to ~/.config/opencode/opencode.json to skip permission prompts:
{ "permission": "allow" }Claude Code
npm install -g @anthropic-ai/claude-codeCodex
npm install -g @openai/codex- Local-first — Avibe runs on your machine; your code and agent processes stay there.
- No public inbound ports — Socket Mode / WebSocket / long-polling only for chat control.
- Your keys, your data — stored under
~/.avibe/, sent only to the AI provider you chose. Existing installs keep~/.vibe_remote/as a compatibility path. - Fail-closed remote access —
avibe.botonly brokers identity and the tunnel, never your data.
vibe stop
uv tool uninstall avibe-os
uv tool uninstall vibe-remote # legacy installs
rm -rf ~/.avibe ~/.vibe_remote- Official Docs — quickstart, concepts, platform & agent guides, troubleshooting
- What is Avibe — the Agent OS model
- CLI Reference · Commands
- Install via AI agent — hand this to Claude Code, Codex, or OpenCode for guided setup
- Slack · Discord · Telegram setup guides
Own the agent. Reach it from anywhere.