vibex

Vibex is a native, local-first workbench for agent-powered software development, built in Rust with the GPUI UI framework and released under AGPL-3.0-or-later (current status 0.1.0-rc.2). The project's stated principle is that the desktop runtime holds authority: agent processes, session history, workspace files, Git, PTYs, providers and permissions all live on the machine you choose. No hosted workspace is required to run the local desktop, and repository, credentials and durable session state stay local. Agent integration is built on the Agent Client Protocol (ACP), which the project describes as its only online agent transport, so any ACP-compatible agent can be connected by registering an executable with its command, arguments, environment and display metadata. Built-in presets are listed for Claude Code, Codex, ZCode and OpenCode, and the ACP catalog additionally names Antigravity, Cline, Codebuddy Code, Cursor, Gemini CLI, GitHub Copilot, Devin, Grok, Hermes, Kimi Code, Pi and DeepSeek Harness, with availability checked against the installed runtime, provider configuration and live capability probes. Documented workflow features include agent sessions rendered as a structured timeline with Markdown, reasoning, plans, tool and process details, attachments, approvals and typed elicitation forms, plus stop, continue, fork, rename and resume, and importing supported local histories. A workspace-scoped file tree supports browsing, name/content search, revision-checked reads and writes, and explicit encoding, line-ending and large-file handling. Git support covers status, history, diffs and blame, branch creation and switching, staging, unstaging, revert, commit, fetch and push, and isolated worktrees with guarded merge and rebase recovery. Native PTYs provide ANSI emulation, tabs, resize, scrollback, search and raw-byte handling, and the workbench previews Markdown, images, PDFs and supported Office documents. A config center manages agent runtimes, model and reasoning selection, provider authentication, health probes, and scoped MCP servers, Skills, Prompts and Hooks. Automation can schedule one-shot, interval or daily agent runs and compose automation graphs with run state, recovery and audit history. Desktop notifications track completed, failed or input-blocked sessions, and timeline state is meant to survive reconnects and restarts. Three native surfaces are described. The desktop app is the full GPUI workbench and authoritative DesktopRuntime for Linux, macOS and Windows. The mobile companion is a native GPUI iOS and Android client that renders the desktop session model as a timeline and sends typed remote mutations; it does not start local agents, own a workspace filesystem, mutate local Git or become a second PTY authority. The optional self-hosted relay is a Rust/Axum service that forwards encrypted WebSocket frames and stores no workspace, provider, agent or application data; pairing can also use Direct or Tailnet routes. Architecturally the runtime is split across crates: core for serialized ids, DTOs, errors, capabilities and remote protocol contracts; desktop-model for framework-neutral session and timeline projections; vibex-backend for provider-neutral capability facades; vibex-ui for semantic tokens and component models; and vibex-remote-client for pairing, reconnect, synchronization and route selection. The stack includes ACP schema 1.6, Tokio, SQLite via rusqlite, xpty and alacritty_terminal, PDFium, and Rustls with X25519, HKDF, HMAC and ChaCha20-Poly1305 for transport. Development requires Git with submodules, Node.js 22, pnpm 11.3.0, Rust 1.97.0 pinned by rust-toolchain.toml and a working Vulkan driver; desktop runs start with pnpm dev:desktop, and mobile builds need the Android SDK/NDK with cargo-ndk or macOS with Xcode and XcodeGen. Repository gates include pnpm check, pnpm release:build-smoke and pnpm check:mobile-native. Privacy notes state that permissions are capability-gated and auditable, provider home configuration is not rewritten by default, and tokens, private keys, prompts, file contents and terminal bytes are excluded from logs and diagnostic artifacts.