Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage background coding agents in tmux sessions. Spawn Claude Code or other agents, check progress, get results.
Manage background coding agents in tmux sessions. Spawn Claude Code or other agents, check progress, get results.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Run coding agents in persistent tmux sessions. They work in the background while you do other things.
AgentCommandBest ForclaudeClaude CodeComplex coding, refactoring, full projectscodexOpenAI CodexQuick edits, auto-approve modegeminiGoogle GeminiResearch, analysis, documentation
AgentCommandBest Forollama-claudeClaude Code + OllamaLong experiments, heavy refactoringollama-codexCodex + OllamaExtended coding sessions Local agents use your Mac's GPU — no API costs, great for experimentation!
./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
tmux list-sessions # or ./skills/tmux-agents/scripts/status.sh
./skills/tmux-agents/scripts/check.sh session-name
tmux attach -t session-name # Detach with: Ctrl+B, then D
tmux send-keys -t session-name "additional instruction here" Enter
tmux kill-session -t session-name
ScenarioRecommendationQuick fix, time-sensitive☁️ Cloud (faster)Expensive task, budget matters🦙 LocalLong experiment, might fail🦙 LocalProduction code review☁️ Cloud (smarter)Learning/exploring🦙 LocalHeavy refactoring🦙 Local
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
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
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
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.