Your agents. Your workspace. Your control — from prompt to commit, desktop to terminal to phone.
A native, local-first AI coding workbench built on the Agent Client Protocol.
Website • Docs • Quick start • Features • Supported agents • Surfaces • Development
| ### Every Agent, one workbench Run Claude Code, Codex, ZCode, OpenCode, and any ACP-compatible Agent side by side. Vibex installs, updates, authenticates, and scopes each runtime, then keeps every session in the same timeline. You can create Agent sessions in Vibex in GUI or TUI mode, whichever you prefer. [Docs →](https://vibex.peatboy.com/docs/agents-and-providers) |
![]()
|
| ### Agent teams and goals The main Agent can delegate work to child Agents on its own, or hand a task to a specific child Agent at the right moment under your guidance. Any Agent Harness that Vibex supports can be a delegation target, which makes cross-Agent delegation possible. [Docs →](https://vibex.peatboy.com/docs/sessions) |
|
| ### Parallel worktrees and Git review Every session can have its own worktree, so concurrent Agents never get in each other's way. Vibex also ships the everyday Changes and Commits workflow, so you can see what an Agent changed in real time at a glance. [Docs →](https://vibex.peatboy.com/docs/git) |
|
| ### Shared Providers and a local gateway Configure a model Provider once and share it across Agents. A route group can hold several model Providers at once, fail over between Providers or models, and translate between OpenAI Chat, OpenAI Responses, Anthropic Messages, and Gemini — so an Agent that only speaks its own protocol can still reach models from other protocols. [Docs →](https://vibex.peatboy.com/docs/providers-and-gateway) |
![]()
|
| ### Terminal, browser, and computer use The Vibex editor can hold files, the terminal, and the browser at once for reading and editing. Agents can also drive the Vibex browser to browse the web, and computer use lets them control the machine — while you watch, approve, and stop them from a dedicated panel. [Docs →](https://vibex.peatboy.com/docs/browser) |
|
| ### Your phone, same session Pair an Android or iOS client (neither is on the app stores yet) with the desktop or a remote instance. Read the same timeline, answer approvals and questions, send follow-ups, browse files and diffs, and use the terminal — vibe coding from anywhere. [Docs →](https://vibex.peatboy.com/docs/remote-mobile) |
|
| ### Vibex TUI The whole workbench in a terminal: sessions, streaming Markdown, approvals, the queue, settings, and pairing. It ships inside every desktop package, works over SSH and tmux, and can attach to the desktop runtime already running on your machine. [Docs →](https://vibex.peatboy.com/docs/tui) |
![]()
|
| ### Remote runtimes, your rules Run Vibex as a remote instance on another machine over SSH or inside WSL2, or self-host `vibex-server` behind HTTPS, a Tailnet, or your own Relay. The desktop, phone, and TUI stay clients; the remote instance serves everything. [Docs →](https://vibex.peatboy.com/docs/ssh-runtime) |
|
| ### Markets, context, and previews Install MCP servers and Skills from in-app markets, write reusable Prompts, and scope each resource per Agent. Read Markdown, PDFs, Office documents, and images in the workbench, with split panes, full-screen previews, and a workbench background that is yours. [Docs →](https://vibex.peatboy.com/docs/mcp-and-skills) |
|
|
Claude Code |
Codex |
ZCode |
OpenCode |
Antigravity |
Cline |
|
Codebuddy |
Cursor |
Gemini CLI |
GitHub Copilot |
Devin |
Grok Build |
|
Hermes |
Kimi Code |
Pi |
DeepSeek Harness |
Any ACP Agent |
More agents coming soon |