Vibe-Switch

Vibe-Switch 是一个 npm 命令行工具，用于并行编排 Claude Code、Codex CLI、Gemini CLI 等 AI 编码代理：为每个任务创建独立 Git 分支与 worktree，提供状态查看、日志跟踪、上下文交接、停止与清理等命令，任务状态保存在本地目录；安装需联网，工具自身运行时不发起网络请求。

brianjhang

热度 43.32

最近更新 2026-05-11 17:42:10

分类：开发依赖：代码执行 / 读写文件应用场景：代码生成 / 工作流 / 任务管理 / DevOps

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add vibe-switch

Metadata

name: Vibe-Switch
description: tmux for AI Agents — Orchestrate multiple AI coding agents in parallel with one command. Run Claude Code, Codex CLI, and Gemini CLI simultaneously on isolated Git branches with seamless context handoff.
version: 1.0.2
tags: ["ai","agent","orchestrator","multi-agent","cli","vibe-coding","tmux","codex","gemini","claude"]
install: {"method":"npm","command":"npm install -g vibe-switch","registry":"https://www.npmjs.com/package/vibe-switch","note":"Installation requires network access to pull the package from npm. After installation, vibe-switch itself runs entirely locally."}
requires: {"binaries":["node (>= 18)","npm","git"],"optional_binaries":["claude (Claude Code CLI — requires ANTHROPIC_API_KEY)","codex (Codex CLI — requires OPENAI_API_KEY)","gemini (Gemini CLI — requires Google Cloud auth)"],"env":["ANTHROPIC_API_KEY (only if using Claude agent — managed by Claude CLI, not by vibe-switch)","OPENAI_API_KEY (only if using Codex agent — managed by Codex CLI, not by vibe-switch)","GOOGLE_APPLICATION_CREDENTIALS (only if using Gemini agent — managed by Gemini CLI, not by vibe-switch)"]}
config_paths: ["~/.vibe-switch/tasks.json (task state store)","~/.vibe-switch/logs/ (agent output logs)","~/.vibe-switch/snapshots/ (handoff context snapshots)",".vibeswitch.json (project-level config, optional)"]
credentials: {"vibe-switch":"none — vibe-switch itself does not read, store, or transmit any API keys or secrets","agent_clis":"each spawned agent CLI manages its own authentication independently; vibe-switch passes only the task prompt as an argument"}
network_access: {"install":"true — npm install requires network","runtime":"false — vibe-switch itself makes no network requests at runtime","spawned_agents":"varies — Claude and Gemini CLIs may access the network; Codex CLI runs in a sandbox with no network access"}
permissions: [{"filesystem":"read/write to ~/.vibe-switch/ for task state, logs, and snapshots"},{"filesystem":"create/remove Git worktrees in sibling directories of the repository"},{"process":"spawns agent CLI subprocesses (claude, codex, gemini) and manages their PIDs"},{"network":"vibe-switch makes zero network requests at runtime; network behavior of spawned agents is controlled by each agent's own configuration"}]
source: https://github.com/brianjhang/vibe-switch
npm: https://www.npmjs.com/package/vibe-switch
license: MIT

Vibe-Switch — tmux for AI Agents

Orchestrate multiple AI coding agents in parallel with one command. Each agent runs in its own isolated Git worktree and branch. When one agent finishes, hand off the context seamlessly to another.

Install

npm install -g vibe-switch

Quick Start

# Start agents in parallel
vibe run "Implement JWT auth middleware" --agent gemini
vibe run "Build responsive login page" --agent codex

# Monitor all agents
vibe status
vibe watch

# Hand off context between agents
vibe handoff vibe/gemini-c3d5 --to codex -m "API is ready at /api/auth"

# Cleanup
vibe stop --all
vibe clean

Command Reference

Command	Description
`vibe run "<task>" --agent <agent>`	Start an agent on an isolated Git branch + worktree
`vibe status`	Display all tasks, status, and branches
`vibe watch`	Real-time multi-agent output streaming
`vibe log <branch> [-f]`	View or follow logs for a specific task
`vibe stop [branch\|--all]`	Stop one or all agents
`vibe handoff <branch> --to <agent>`	Transfer context to another agent
`vibe summary <branch>`	View task summary, logs, and diff stat
`vibe clean`	Clean up completed tasks, logs, and worktrees
`vibe agents`	List installed agent adapters
`vibe doctor`	Diagnose environment and agent availability
`vibe init`	Create project config `.vibeswitch.json`
`vibe config [key] [value]`	View or set project config

Supported Agents

Agent	Command	Sandbox	Best For
Claude Code	`claude`	No	Architecture, code review, broad reasoning
Codex CLI	`codex`	Yes	Implementation, refactors, test-driven changes
Gemini CLI	`gemini`	No	Exploration, cross-checking, documentation
Antigravity	`antigravity`	No	Full-stack development, complex tasks
OpenClaw	`openclaw`	No	General purpose AI coding

Architecture

Git Worktree Isolation: Each agent runs in a dedicated branch and directory — no file conflicts.
Adapter Pattern: Modular design for easy integration of new AI agent CLIs.
JSON File Storage: Task metadata persisted locally at ~/.vibe-switch/ — no database needed.

Common Workflow Patterns

Parallel Development

vibe run "Implement auth API and migration" --agent claude --branch vibe/auth-api
vibe run "Build auth UI and form validation" --agent codex --branch vibe/auth-ui
vibe run "Write integration tests for login" --agent gemini --branch vibe/auth-tests
vibe status
vibe watch

Context Handoff

# Gemini finished the API → hand off to Codex for the frontend
vibe handoff vibe/auth-api --to codex -m "API complete. Build the client-side integration."

Agent Capability Matrix

Agent	Local Files	Network/SSH	Sandbox
claude	✅	✅	No
codex	✅	❌	Yes
gemini	✅	✅	No

Important: Codex runs in a strict sandbox — no SSH, no external APIs. Do not assign deployment or network-dependent tasks to Codex.

Key Constraints

Must be run from inside a Git repository.
Worktrees are based on the current branch HEAD — uncommitted changes are NOT visible to spawned agents. Always git add && git commit before dispatching.
Right-size your tasks: if it takes less than 5 minutes and touches one file, do it yourself.