See at a glance which tmux sessions have Claude/Codex working vs idle
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 28/100. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Codex
Model
Claude
Fastest way to find out if tmux-agent-status belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/samleeney/tmux-agent-status ~/.claude/agents/tmux-agent-statusRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/tmux-agent-statusNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ tmux-agent-status/ ← installs here └─ settings.json
See at a glance which tmux sessions have Claude/Codex working vs idle
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: June 24, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.