Skip to content

Repository files navigation

AgentMux

test Python 3.10+

Run a full multi-agent software pipeline using the AI subscriptions you already have.

Website & Docs: https://markuswondrak.github.io/AgentMux/

AgentMux orchestrates a structured PM → Architect → Plan → Code → Review → Done workflow across claude, codex, gemini, opencode, copilot, and qwen — driving them through tmux, not the API. No pay-per-token. No new credentials. Just your existing CLI tools working in concert.


agentmux ---

Why AgentMux

  • No API costs — injects prompts into tmux panes, reusing your existing Claude, Codex, Gemini, OpenCode, Copilot CLI, or Qwen subscriptions. No tokens billed to you directly.
  • Structured pipeline — a deterministic state machine moves work through planning, implementation, and review phases. Agents don't freelance; they execute focused roles.
  • Mix providers per role — run the architect on Claude Max, the coder on Codex, and the reviewer on Gemini. Each role is independently configurable.
  • Watch it work — the session is a live tmux window. Attach at any time to observe, intervene, or take over.
  • GitHub-native — bootstrap from an issue, auto-open a pull request when the pipeline completes.

Quickstart

# Install with pipx (recommended)
pipx install git+https://github.com/markuswondrak/AgentMux.git

# Initialize a project (interactive setup)
cd your-repo
agentmux init

# Run a feature from description to reviewed, committed code
agentmux "Add rate limiting to the API"

# Bootstrap from a GitHub issue
agentmux issue 42

# Resume an interrupted run
agentmux resume

For a full walkthrough, see the Getting Started guide.

How it works

AgentMux creates a tmux session with a control pane and one pane per agent role. A file-watching orchestrator tracks session artifacts written by agents and advances the workflow state machine when the right files appear. Agents coordinate through a shared file protocol — they never talk to each other directly. The orchestrator decides what happens next and injects the appropriate prompt into the right pane.

Configuration

Project config lives in .agentmux/config.yaml. Run agentmux init to scaffold it interactively, or create it manually:

version: 2

defaults:
  provider: claude
  model: sonnet

roles:
  architect:
    model: opus
  coder:
    provider: codex
  reviewer:
    model: sonnet

Config is resolved in layers: built-in defaults → ~/.config/agentmux/config.yaml → project config → --config <path>. See docs/configuration.md for the full schema.

Supported providers

Provider CLI tool
claude Claude Code CLI
codex OpenAI Codex CLI
copilot GitHub Copilot CLI
gemini Google Gemini CLI
opencode OpenCode CLI
qwen Qwen CLI

Agent roles

Role When active
product-manager Optional first phase for requirements refinement
architect Planning and replanning
coder Implementation and fixes
reviewer Review and final confirmation
code-researcher On-demand codebase analysis
web-researcher On-demand internet research

Requirements

  • Python 3.10+
  • tmux
  • One or more supported AI CLI tools installed and authenticated

Documentation

About

Deterministic multi-agent pipeline for end-to-end software development, orchestrating CLI-based AI tools (e.g. Gemini, Claude, Codex) through tmux-controlled sessions.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages