Build from source

Build any part of VibeAround — the standalone server, the CLI tools, or the full desktop app — from a checkout. This is the supported path for macOS Intel and for development.

Prerequisites

• Rust (stable toolchain) — the workspace has seven crates
• Bun — drives the JS builds and workspace scripts
• Node.js — runtime for channel plugins and agent ACP adapters
• Tauri system dependencies — only for the desktop app (Tauri prerequisites per platform: Xcode CLT on macOS, MSVC on Windows, webkit2gtk on Linux)

All build commands below run from src/ in the repository.

Standalone server + dashboard

bun install
bun run web:build        # dashboard SPA → web/dist
cargo build --release -p server

Run it with the built dashboard:

cargo run --release -p server    # binds 127.0.0.1:12358

CLI, TUI, and launcher

bun run va:build         # cargo build -p va-cli -p va-tui -p va-launcher

Binaries land in target/debug/ (or --release): va, va-tui, va-launch. Note va launch execs a sibling va-launch binary — keep them in the same directory, as the packaged distributions do.

Desktop app

bun install
bun run build            # desktop-ui + web SPA, then tauri build

Development mode with hot reload for the UI:

bun run dev              # tauri dev (desktop-ui served by vite)

The Tauri build prepares va-launch as a sidecar binary automatically (scripts/prepare-va-launch.mjs) and bundles per-platform packages (DMG/EXE/MSI/AppImage/deb).

Running tests

cargo test --workspace
cargo clippy --workspace -- -D warnings

JS surfaces build-check with bun run web:build and bun run desktop-ui:build.

tmux integration (optional)

The web terminal can attach to tmux sessions when tmux is installed — no build flag needed; it is detected at runtime. The tmux_detach_others setting controls whether attaching from the dashboard detaches other clients.

What you cannot build without maintainer secrets

Release packaging beyond a local unsigned build uses maintainer-private configuration that is deliberately not in the repository:

• macOS signing/notarization (apple-sign config) — local DMGs work unsigned but Gatekeeper will warn.
• The release build script (build.sh) and update-channel publishing.

Everything needed for a fully functional local build is public; only distribution signing is private.

Plugins and SDK

Channel plugins and @vibearound/plugin-channel-sdk are separate repositories with their own npm-based builds (npm, not bun, in those repos). See Build a channel plugin.

Source anchors: src/package.json (build scripts), src/Cargo.toml (workspace members), src/scripts/prepare-va-launch.mjs (sidecar), src/npm/cli/ (npm packaging). Last verified: v0.7.11