VibeAround Documentation
A progressive guide for installing, using, configuring, operating, and understanding the VibeAround workspace for local AI coding agents.
VibeAround is a workspace for AI coding agents. It helps you launch agents with the right model profile, continue sessions from desktop, browser, mobile, terminal, or messaging entry points, and preview what agents build — while the real repository and execution environment stay on your own computer.
This documentation is organized for several kinds of readers. New users can follow the start path without knowing the architecture. Daily users can learn the core workflows. Operators can configure providers, channels, tunnels, and security controls. Maintainers can study the technical model and local development flow.
Reader Paths
| Reader | Start with | Continue with |
|---|---|---|
| First-time user | Installation | Quick Start, Download |
| Daily agent user | Agent Launch | Unified Workspace, Session Handover |
| Remote-work user | Remote Messaging & Web Terminal | Live Preview, Security Model |
| Provider/config owner | Provider Profiles & API Bridge | Supported Providers, Supported AI Agents |
| Maintainer | Architecture | Develop Locally, Troubleshooting |
What VibeAround Coordinates
VibeAround sits around tools you already choose. It does not replace your repository, terminal, model provider, or agent CLI. It gives those pieces a shared control layer:
- Launch Claude Code, Codex CLI, Gemini CLI, Pi, OpenCode, Claude Desktop, Codex Desktop, and related agents from one place.
- Select a workspace, terminal mode, model profile, API endpoint, and previous session before starting work.
- Keep sessions reachable from the desktop app, web dashboard, Web Chat, Web Terminal, mobile browser, and supported messaging channels.
- Preview local dev servers, Markdown, HTML, and generated artifacts through owner links or scoped share links.
- Keep execution local by default, with explicit controls for tunnels, browser pairing, tokens, and channel integrations.
Documentation Shape
Every page is a practical guide: real commands, verified configuration fields, and troubleshooting for the failure you are actually seeing.
Use the left navigation as the source of truth. Core content should live in documentation pages, not behind homepage anchors.