Skip to main content

​
Setup wizard

Run:
Avibe starts a local Web UI and opens the setup wizard.

​
What you configure

The wizard has three screens:
  1. Introduction — how Vibey and the other assistants work together: Vibey coordinates Claude Code, Codex, and OpenCode. Select Get started.
  2. Add model providers — add a subscription or an API key to Model Hub.
  3. Choose your AI assistants — give Vibey a model, enable Claude Code, Codex, or OpenCode, and select Enter workspace.
Entering the workspace completes setup, so you are not sent back to the wizard on the next launch. You can change anything later in Settings.

​
Model providers

The wizard routes every assistant through Model Hub, Avibe’s local model gateway, and installs and starts it if needed. Select Add subscription or API Key to sign in with a subscription or paste an API key. For Vibey, use an API key or choose Sign in as a gateway source: a subscription used natively by its own CLI does not supply Vibey. If Avibe detects API keys you already have configured, it offers to migrate them instead of making you retype them. Add at least one source, then select Continue to assistants. As the Model Hub card puts it: Connect once, share with every assistant.

​
Agent backends

The Choose your AI assistants screen: Vibey's card first, then Claude Code, Codex, and OpenCode, each with its default model

Product UI, sample project data.

The Choose your AI assistants screen shows one card per assistant: Vibey first, then Claude Code, Codex, and OpenCode.
  • Vibey is built in, so its card reads Built-in · always on and has nothing to install or enable. Until it has a model, the card says No model yet. Pick one to start. and offers models your sources supply, plus All models…. Vibey alone can complete setup once it has a model. See Vibey.
  • Claude Code, Codex, and OpenCode run their official CLIs unchanged. The wizard detects which are installed, offers a one-click install for any that are missing, and lets you enable each one. An enabled assistant shows the model route it will use; Configure model route opens it for review. If OpenCode is set to stop and approve every tool call, its card offers Allow tool calls.
To enter the workspace, give Vibey a model or enable an assistant that can reach one: Pick a model for Vibey, or enable an assistant, to enter the workspace. You can enable multiple backends and route different channels to different agents.

​
The Avibe Workbench is always available

You do not need a third-party chat app to use Avibe. The Avibe Workbench is a built-in web chat that lives in the local Web UI and is always enabled — it is the one surface you cannot turn off. Connecting Slack, Discord, and the others is optional and additive. On a phone, open the Workbench URL and use your browser’s Add to Home Screen to install it as an app.
Workbench-only is a complete setup. The wizard does not ask for a chat platform; add one later when you want it.

​
Chat platforms (optional)

Connect the chat app where you already work in Settings > Messaging Platforms. Each platform has its own credential step.

​
Prefer the wizard over manual config

Avibe stores persistent config under your local user directory. You can inspect config files when debugging, but first-time setup should go through the wizard because it validates credentials and model connections.