Governed Vibecoding vs Unmanaged AI CodingRead Now →
Skip to main content
VibeFlow CLI

One terminal. Every AI coding agent.
Zero chaos.

Open-source, Go-based session manager that lets engineering teams run Claude Code, OpenAI Codex CLI, and Google Gemini CLI side-by-side in isolated tmux + git worktree environments — with optional server-connected autonomous task execution via VibeFlow.

View on GitHubInstall
Apache License 2.0Single Go binarymacOS + Linux
VibeFlow CLI terminal interface showing multiple AI coding sessions with session list, live output preview, and keyboard shortcuts

Install in one line

Requires Go 1.25+ and tmux 3.2+. Everything else is embedded in the binary.

Quick install
go install vibeflow-cli/cmd/vibeflow@latest

Then run vibeflow to launch the TUI.

Build from source
git clone https://github.com/axiom-studio/vibeflow-cli.git
cd vibeflow-cli
go build -o vibeflow ./cmd/vibeflow

Full Go source — inspectable, auditable, forkable.

Everything you need to run a team of AI agents

A wizard-driven launch flow, isolated runtime environments, built-in error recovery, and a bundled Claude Code Plugin — all shipped as a single Go binary.

Multi-Session Management

Launch every AI coding session from a single TUI. See every session's provider, branch, persona, and status at a glance — and switch between them with one keypress.

Any AI Coding Agent

First-class support for Claude Code, OpenAI Codex CLI, and Google Gemini CLI. Extend the built-in templates with any custom agent binary through YAML configuration.

Persona-Based Teams

Assign specialized personas — Developer, Architect, QA Lead, Security Lead, PM, Principal Engineer — so several agents can collaborate on the same repo without stepping on each other.

Git Worktree Isolation

Every session runs in its own git worktree on its own branch. No merge conflicts between concurrent agents. Configurable cleanup when sessions end.

Autonomous Execution

Opt into VibeFlow server mode and agents become fully autonomous — polling tasks, implementing, committing, and reporting back while you supervise.

Single Go Binary

Zero external dependencies beyond tmux. Providers, launch templates, agent docs, and the full TUI are all embedded. Runs on macOS and Linux out of the box.

Session Conflict Detection

If two agents try to target the same directory, VibeFlow offers four clean resolutions: switch to existing, create a new worktree, clean up the stale session, or cancel.

Error Recovery Pipeline

Pattern registry, health monitor, and auto-recovery with exponential backoff handle 429/529/5xx gracefully. Dead sessions restart with one tap, full original parameters restored.

Auto-Embedded Agent Docs

CLAUDE.md, AGENTS.md, and GEMINI.md are auto-copied into the working directory on launch, so every agent picks up project conventions before writing a line of code.

Open source

Inspectable, auditable, forkable

Every line of code, every agent doc, every provider template lives in a public repository you control. No hidden binaries. No mandatory SaaS.

github.com/axiom-studio/vibeflow-cli

Apache License 2.0

Permissive, commercially friendly, with an explicit patent grant. Read the LICENSE file in the public repo.

Zero lock-in

Vanilla mode works fully standalone with no VibeFlow server account. Autonomous mode is optional, additive capability — never a gate.

Inspectable agent docs

Every behavioral rule an agent follows lives in `vibecoding-agent-docs/` in the public repo. Read, audit, fork, and extend.

Config-extensible

Providers, launch templates, worktree strategies, and error recovery live in `~/.vibeflow-cli/config.yaml`. Add a new agent without recompiling.

Without vs. with VibeFlow CLI

The day-to-day difference between juggling terminal tabs and running a managed multi-agent workflow.

Separate terminal tabs per agent, no visibility across sessions
Single TUI listing every session across every project and branch
Manual `git worktree add` dance, then manual cleanup
Wizard-driven worktree creation with configurable cleanup-on-kill
Hand-rolled flag strings per agent (`--dangerously-skip-permissions`, `--yolo`, `-p`)
Built-in provider templates — correct flags for every supported agent
Two agents stomp on the same working tree — corrupted commits
Session conflict detection with four clear resolution options
Agent docs copy-pasted by hand into each repo
Auto-embedded on session launch from an embedded source of truth
An agent dies on a 529 and stays dead
Error pattern registry + exponential backoff + auto-recovery
Dead sessions after a reboot require full re-setup
Session cache persists; one-tap restart restores full parameters

Who it's for

From a solo developer running three agents on three branches to a platform team standardizing AI coding across an entire org.

Individual developers running multiple AI agents

Stop losing track of which terminal tab has which agent on which branch. Launch every Claude/Codex/Gemini session from one wizard, switch with a single keypress, and never accidentally point two agents at the same working tree.

Platform & developer experience teams

Standardize how your engineering org runs AI coding agents. Ship one CLI, one config format, one set of session rules — and get tmux isolation, worktree hygiene, persona assignments, and error recovery for free.

Open-source-conscious engineering orgs

Apache 2.0, public repo, inspectable agent docs, no mandatory SaaS dependency. Self-host the server component or run fully local in Vanilla mode — every behavior your agents follow can be read, audited, and forked.

Teams building autonomous agent pipelines

The VibeFlow server integration turns personas into a lightweight orchestration layer. Run Developer and Architect agents on the same feature, each picking up work items filtered to its role, without either blocking the other.

Frequently asked questions

Everything you need to know before installing.

What is VibeFlow CLI?
VibeFlow CLI is an open-source, Go-based terminal UI and command-line tool that turns chaotic, multi-agent AI coding workflows into a single managed surface. It lets engineering teams run Claude Code, OpenAI Codex CLI, and Google Gemini CLI side-by-side in isolated tmux + git worktree environments, with optional server-connected autonomous task execution via VibeFlow.
Is VibeFlow CLI open source?
Yes. VibeFlow CLI is distributed under the Apache License 2.0 — a permissive, commercially friendly license with an explicit patent grant. The full source, agent docs, and configuration templates are available at github.com/axiom-studio/vibeflow-cli. Every behavioral rule an agent follows is inspectable and auditable in the public repository.
Which AI coding agents does VibeFlow CLI support?
VibeFlow CLI has first-class support for Claude Code, OpenAI Codex CLI, and Google Gemini CLI — each agent's autonomous flags, prompt-passing conventions, and binary quirks are handled out of the box. You can also extend the built-in provider templates to register any custom agent binary through YAML configuration without recompiling.
How do I install VibeFlow CLI?
The fastest path is `go install vibeflow-cli/cmd/vibeflow@latest`, which requires Go 1.25 or later and tmux 3.2 or later. You can also clone the repository at github.com/axiom-studio/vibeflow-cli and build from source with `go build -o vibeflow ./cmd/vibeflow`. The result is a single binary with everything embedded — no external dependencies beyond tmux.
Do I need a VibeFlow server to use the CLI?
No. Vanilla mode works fully standalone with zero VibeFlow server account and zero network dependency — you get multi-session management, git worktree isolation, tmux sockets, clipboard passthrough, and error recovery out of the box. Connecting to a VibeFlow server is optional and unlocks autonomous task polling, persona-based multi-agent workflows, and the LLM Gateway — all additive, never gated.
How does VibeFlow CLI isolate multiple agents?
Every session runs in its own git worktree on its own branch, so two concurrent agents never corrupt each other's working tree. tmux sockets are scoped per root directory (via `--root` or `VIBEFLOW_ROOT`), so parallel VibeFlow instances get independent sockets, config, logs, PID locks, and session caches. If two agents try to target the same directory, VibeFlow surfaces a conflict popup with four resolution options: switch to existing, create a new worktree, clean up the stale session, or cancel.
What happens if an agent crashes or a session dies?
VibeFlow CLI ships with a pattern registry, health monitor, and auto-recovery pipeline that handles 429/529/5xx errors with exponential backoff and configurable retry limits. Session cache survives process kills — on startup, dead sessions are surfaced in a multi-select popup for one-tap restart with the full original parameters (init prompt, LLM gateway, skip-permissions flag).
How does VibeFlow CLI differ from running agents directly in tmux?
Running agents directly in tmux leaves you managing flag strings, worktree cleanup, agent docs, and dead sessions by hand. VibeFlow CLI gives you a 10-step guided launch wizard, built-in provider templates with correct flags for every supported agent, auto-embedded agent docs, configurable worktree cleanup, session conflict detection, grouped and flat view modes, a non-blocking server health probe, and a bundled Claude Code Plugin with MCP config, skills, agents, and hooks.
What platforms does VibeFlow CLI run on?
VibeFlow CLI runs on macOS and Linux — any developer laptop or CI box that can host an interactive shell with Go 1.25+ and tmux 3.2+. It includes clipboard passthrough on macOS so paste works correctly inside tmux-wrapped agents.

VibeFlow CLI is the terminal companion to VibeFlow, the full AI engineering team platform. For agent tool governance see the MCP Gateway, and for model access see the LLM Gateway. Learn more on the Axiom blog.

See It In Action

Contact Us

See how AXIOM gives your enterprise complete control over AI operations, compliance, and costs.

No spam, ever. We respect your inbox.

Protected by reCAPTCHA Enterprise. Privacy · Terms