Avibe

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

Every agent. Every subscription. Running on your machine, steered from your pocket.

Docs · English · 中文

Agents

Reach it from

Vibey, Avibe's own agent

Avibe ships its own official agent, Vibey: built in, always on, nothing extra to install. Add a model source to Model Hub — a subscription sign-in or an API key — give Vibey a model, and it is ready in the Workbench and in every chat app you connect.

• It runs the platform for you. Vibey schedules Tasks, waits on Watches, builds Show Pages, and hands parts of a job to Claude Code, Codex, or OpenCode — all through the same vibe commands every agent uses.
• It codes. It reads, writes, and edits files and runs commands (bash on macOS and Linux, PowerShell on native Windows). Independent tool calls in one response run at the same time, and a long command becomes a Watch that reports back to the same session.
• It keeps going. Fork a session, stop a turn, keep talking: when a conversation grows long, Vibey condenses the earlier part without interrupting you.

Already have favorite agents? Avibe also runs the official Claude Code, Codex, and OpenCode unchanged, side by side with Vibey. → Vibey docs

Your agent is a genius — chained to a terminal

Claude Code, Codex, and OpenCode are absurdly capable. But:

• 🖥️ Close the lid, lose the agent. It lives in one terminal window. Walk away and the work stops with you.
• 📵 Out of sight, out of control. Away from your desk, you can't see what it's doing — let alone steer it.
• 💸 Paying for several plans, stuck on one. One hits its cap mid-task while another sits idle, and you have no idea which one is earning its keep.
• 🔒 Every tool wants to own you. Its app, its cloud, its subscription — and your code on someone else's box.

Avibe sets it free

One command, and your machine becomes the home your AI partner lives in. Drive the official Claude Code, Codex, and OpenCode from a browser, your phone, or the chat app you already have open. Your Claude, ChatGPT, Gemini, Kimi, and xAI subscriptions and your API keys all land behind one local gateway. Your code, keys, and agent processes stay on your machine — avibe.bot signs you in and opens a secure tunnel, and never touches your workspace.

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

The browser pops open. A three-step wizard wires up your models, finds your agents (one click installs any that are missing), and drops you straight into the Workbench.

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

💬 Not a chat box. A whole Workbench.

Files, editor, and terminal open as windows beside your chat, all in one browser tab — with the apps and Show Pages your agent builds opening right next to them. It stops feeling like a web page and starts feeling like an operating system.

🔀 Model Hub — every plan you pay for, finally on the same team

Sign in each subscription and add each API key once — official vendors, relays, aggregators, self-hosted endpoints, all welcome. Switch an agent to gateway mode and Avibe's local gateway routes its models through them in the order you set.

• Set up once, use it in every agent. One gateway-held sign-in or key feeds Claude Code, Codex, and OpenCode at the same time — no copying credentials into three configs. (A subscription you leave to its own CLI serves only that CLI.)
• Mix and match models. GPT inside Claude Code, Claude inside Codex — put any gateway-held source's models on any agent's list, and the gateway translates between protocols.
• Plan runs dry? The next one picks it up. If a source hits a quota, rate limit, or network failure before it starts answering, the next source in your route takes the request — no retry, no babysitting. Once your first choice recovers, the next turn goes back to it.
• Route it your way. Give each agent a default source order, then pin any single model to its own route chain.
• Move in with one click. Already signed in to a supported CLI? Bring that login over with your explicit OK. Credentials and routes stay on your machine.

Four sources feeding three agents: GPT and Claude models mixed in every agent, and relay-gpt already covering for Codex's unavailable subscription.

Know exactly what your plans are worth. Usage trends by model and source, and your usage priced at official API rates. For Claude and ChatGPT subscriptions, add live 5-hour and weekly quotas — down to how many times over each plan has already paid for itself.

One real day on the maintainer's machine: ~680M tokens, worth ~$540 at official API prices.

⏰ It works while you sleep — the Agent Harness

Most AI tools freeze the moment you stop typing. Avibe gives your agent four durable primitives — run, schedule, watch, and inspect — so it starts work on its own, waits for the right moment, grinds away in the background, and comes back when there's something worth your attention. Scheduled shell commands stay silent when they pass; a failure leaves a notice — or, if you opt in, goes straight to an Agent.

No flags to learn. Just say it:

• "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."

🤖 The real agents, not knock-offs

Avibe runs the official Claude Code, Codex, and OpenCode CLIs — the same ones you'd install yourself — behind one Agent registry. Give each Agent its own model and reasoning effort, and hand each project or channel to the right specialist. Write a Skill once; all three backends load it the same way.

When your agents start delegating to each other, Runs draws the whole chain as a graph: who started each background Session, where it reports back, and the history behind every node.

🎨 Show Pages — your agent answers with a web page

Ask for a dashboard, flowchart, diff, report, or small app, and get a live page instead of a wall of text. Click an element, box a region, or mark up a screenshot with numbered notes, say what you want, and the agent reworks the page or answers right where you pointed.

Keep a page private, or