workmux

Manages git worktrees paired with tmux windows as isolated development environments.

4|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/okm321/dotfiles --skill workmux-okm321
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workmux
Source: https://github.com/okm321/dotfiles/tree/main/claude/skills/workmux
Command: npx skills add https://github.com/okm321/dotfiles --skill workmux-okm321

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running multiple AI agents or parallel development tasks in one repository causes branch conflicts and tangled terminal state. workmux isolates each task in its own git worktree with a dedicated tmux window, branch, and agent, so parallel work stays separated and trackable. ## Core Features & Use Cases - Worktree lifecycle management: Create, list, open, merge, and remove git worktrees with a single command, including automatic branch cleanup and tmux window handling. - Multi-agent orchestration: Check agent status, wait for completion, capture terminal output, and send instructions to agents running in other worktrees, even across projects. - Configurable environments: Define pane layouts, file copies/symlinks, post-create hooks, and merge strategies via global and project-level YAML config. - Use Case: Dispatch three bug-fix tasks to parallel Claude agents with workmux add -b -P prompt.md, monitor them with workmux status, then merge each finished branch back with workmux merge. ## Quick Start Ask the AI to create a new workmux worktree for a branch named 'fix-login' with a prompt describing the bug to fix.

Frequently Asked Questions about workmux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a git worktree with a tmux window using workmux?▼

Run `workmux add <branch-name>` to create a git worktree, run configured file operations and hooks, and open a tmux window with your pane layout. Use `-b` to create it in the background and `-P <file>` to pass a prompt to the agent pane.

How do I run multiple AI agents in parallel on the same repo?▼

Create one worktree per task with `workmux add -b -P prompt.md`, optionally using `-n <count>` or `--foreach` for batches. Each worktree gets its own branch and tmux window, and you can monitor all agents with `workmux status` or `workmux dashboard`.

Can workmux send instructions to an agent running in another project?▼

Yes, `workmux send` targets agents by worktree handle and searches all active agents globally if the handle is not in the current repo. Use `project:handle` syntax, such as `workmux send myproject:docs "update the API section"`, to disambiguate cross-project targets.

Which AI agents does workmux support for prompt injection?▼

workmux auto-detects claude, gemini, codex, opencode, kiro-cli, and vibe in pane commands and injects prompts automatically. The `<agent>` placeholder in config resolves to whichever agent you set as the default.

What happens to the branch and tmux window when I merge with workmux?▼

By default `workmux merge` merges the branch into the base, deletes the tmux window, removes the worktree, and deletes the local branch. Use `--keep` to retain the worktree, window, and branch after merging.