tmux-agents

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "tmux-agents" with this command: npx skills add thinkfleetai/thinkfleet-engine/thinkfleetai-thinkfleet-engine-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 ThinkFleet 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

flyio-cli-public

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

playwright-cli

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

github

No summary provided by upstream source.

Repository SourceNeeds Review