Local-first architecture

Avibe runs on your machine. Your codebase, working directory, agent CLI, agent process, logs, and local configuration stay local. Local-first is an architectural stance, not a setting — see Design Philosophy.

Data flow

You
  -> chat app
  -> Avibe on your machine
  -> Claude Code / OpenCode / Codex
  -> Avibe
  -> chat app
  -> You

Avibe is the local runtime that lets your AI colleague live in chat while the actual agent work stays on your machine. It does not add a hidden LLM loop between you and your chosen agent.

Why this matters

No hosted coding VM is required.
No public inbound port is required for normal chat control.
The agent sees the same local project state you would see in a terminal.
Token overhead stays near zero because Avibe does not act as a second reasoning agent in front of your chosen agent.

What leaves your machine

Your code at rest, working directory, Agent process, logs, local configuration, and local Agent credentials stay on your machine. Local-first does not mean offline-only. This table is the authoritative boundary inventory. It covers every network path that carries user content or metadata derived from that content, in every available mode. A new path must be added here before it ships. In this inventory, Memory provider data means Memory inputs and all content derived from them. Its current forms are messages, search queries, distilled Memory snippets or candidates used for reranking, and eligible attachment copies.

Path	Personal Avibe	Enterprise-managed Avibe
Chat apps and Remote Web UI	Messages pass through the chat service you choose. Remote Web UI browser traffic returns to your machine through its secure tunnel; the avibe.bot application authenticates access but does not proxy that browser content.	Same boundary.
Agent model calls	Your Agent sends task prompts and context to its configured AI provider. Agent and Model Hub credentials stay on your machine.	Same boundary. Organization Model Service settings do not change your Agent models.
Voice input	Audio and transcript-cleanup text go through avibe.bot to Avibe’s cloud models.	Audio and transcript-cleanup text go through avibe.bot to the provider configured by your organization.
Cloud Memory	The personal default sends Workbench messages, authorized users’ private messages, search queries, and eligible attachment copies through avibe.bot to Avibe’s cloud models.	The same Memory content goes through avibe.bot to the provider configured by your organization.
Custom Memory endpoints	Memory provider data, as defined above, goes directly to the providers you configure. Their API keys stay on your machine.	New custom configuration is unavailable. An existing working configuration can continue until the organization supplies a complete replacement; while it runs, it uses the same direct boundary.
Platform free pool	This is the default model source for personal Voice input and cloud Memory. Avibe’s cloud models process the Voice and Memory content listed above.	Never used as a fallback. Missing organization models surface as unavailable instead.
Organization BYOK credentials	Not used.	Provider API keys entered in Config Center are encrypted at rest on avibe.bot, cannot be read back, and stay bound to the endpoint addresses they were saved for. They are used only by Model Service on the server.
Model Service usage records	avibe.bot stores per-instance token-count metadata for Model Service calls.	Same boundary; organization usage is still attributed by Avibe instance.

The distilled Memory store and search index remain local. Messages and eligible attachment copies also remain in the local queue while waiting to process. Each external platform or provider handles the traffic it receives under its own policies.

What avibe.bot is for

avibe.bot provides the hosted control plane for secure remote Web UI access and the separate Model Service for Voice input and Memory. When you run:

vibe remote

Avibe helps pair your local Web UI with an authenticated remote URL. Browser traffic goes through the tunnel to your local machine rather than through the avibe.bot application. Your codebase and agent runtime remain local. Access is fail-closed — auth, routing, and host checks default to deny — so a misconfiguration locks you out rather than exposing your machine.

Start here

avibe.bot Cloud

Self-hosting

Platforms

Agents

Concepts

Reference

Compare

Local-first architecture

Local-first architecture

Data flow

Why this matters

What leaves your machine

What avibe.bot is for

​Local-first architecture

​Data flow

​Why this matters

​What leaves your machine

​What avibe.bot is for

Local-first architecture

Data flow

Why this matters

What leaves your machine

What avibe.bot is for