Tmux Agents

Manage background coding agents in tmux sessions. Spawn Claude Code or other agents, check progress, get results.

cuba6112

@cuba6112

What This Skill Does

Manages background coding agents in persistent tmux sessions. Spawns Claude Code, OpenAI Codex, Google Gemini, or local Ollama agents to run tasks asynchronously, then check progress and retrieve results.

Replaces manually juggling multiple terminal windows or losing agent output when a session closes.

When to Use It

  • Spawn a Claude Code agent to refactor a large codebase in the background
  • Run multiple parallel coding tasks (e.g., backend, frontend, tests) simultaneously
  • Use a free local Ollama agent for long experiments without API costs
  • Check the status of all running agent sessions with a single command
  • Send additional instructions to a running agent without restarting it
  • Kill a completed or stuck agent session to free system resources

Install

$ openclaw skills install @cuba6112/tmux-agents

Tmux Agents

Run coding agents in persistent tmux sessions. They work in the background while you do other things.

Available Agents

☁️ Cloud Agents (API credits)

AgentCommandBest For
claudeClaude CodeComplex coding, refactoring, full projects
codexOpenAI CodexQuick edits, auto-approve mode
geminiGoogle GeminiResearch, analysis, documentation

🦙 Local Agents (FREE via Ollama)

AgentCommandBest For
ollama-claudeClaude Code + OllamaLong experiments, heavy refactoring
ollama-codexCodex + OllamaExtended coding sessions

Local agents use your Mac's GPU — no API costs, great for experimentation!

Quick Commands

Spawn a new agent session

./skills/tmux-agents/scripts/spawn.sh <name> <task> [agent]

# Cloud (uses API credits)
./skills/tmux-agents/scripts/spawn.sh fix-bug "Fix login validation" claude
./skills/tmux-agents/scripts/spawn.sh refactor "Refactor the auth module" codex
./skills/tmux-agents/scripts/spawn.sh research "Research caching strategies" gemini

# Local (FREE - uses Ollama)
./skills/tmux-agents/scripts/spawn.sh experiment "Rewrite entire test suite" ollama-claude
./skills/tmux-agents/scripts/spawn.sh big-refactor "Refactor all services" ollama-codex

List running sessions

tmux list-sessions
# or
./skills/tmux-agents/scripts/status.sh

Check on a session

./skills/tmux-agents/scripts/check.sh session-name

Attach to watch live

tmux attach -t session-name
# Detach with: Ctrl+B, then D

Send additional instructions

tmux send-keys -t session-name "additional instruction here" Enter

Kill a session when done

tmux kill-session -t session-name

When to Use Local vs Cloud

ScenarioRecommendation
Quick fix, time-sensitive☁️ Cloud (faster)
Expensive task, budget matters🦙 Local
Long experiment, might fail🦙 Local
Production code review☁️ Cloud (smarter)
Learning/exploring🦙 Local
Heavy refactoring🦙 Local

Parallel Agents

Run multiple agents simultaneously:

# Mix and match cloud + local
./scripts/spawn.sh backend "Implement user API" claude           # Cloud
./scripts/spawn.sh frontend "Build login form" ollama-codex      # Local
./scripts/spawn.sh docs "Write API documentation" gemini         # Cloud
./scripts/spawn.sh tests "Write all unit tests" ollama-claude    # Local

Check all at once:

./skills/tmux-agents/scripts/status.sh

Ollama Setup

Local agents require Ollama with a coding model:

# Pull recommended model
ollama pull glm-4.7-flash

# Configure tools (one-time)
ollama launch claude --model glm-4.7-flash --config
ollama launch codex --model glm-4.7-flash --config

Tips

  • Sessions persist even if Clawdbot restarts
  • Use local agents for risky/experimental work
  • Use cloud for production-critical tasks
  • Check tmux ls to see all active work
  • Kill sessions when done to free resources

Top skills in this category