Problem solved

Developers running several coding agents in parallel typically rely on separate terminal windows or generic multiplexers, where pane status is inferred only from the shell prompt and cannot tell you whether an agent job is still running, finished, or blocked awaiting input. termany addresses this by tracking job-level state per pane and surfacing working, done, and needs-attention statuses, so users can spot the session that requires their attention without polling every window.

Use cases

• Run multiple coding agent sessions side by side in one terminal window
• See which agent job has finished and which one needs input before switching panes
• Review diffs produced by agents working in separate git worktrees
• Manage ports for dev servers and other processes launched inside agent panes
• Monitor and drive agent sessions running on remote hosts
• Keep long-running agent jobs visible while continuing other terminal work

Audience

• Developers
• ML Engineers
• Hobbyists

Pros

• Pane status is derived from the running job rather than from shell prompt parsing
• Single-window management of many concurrent agent sessions
• Includes diff, git worktree, and port handling tailored to agent workflows
• Supports remote hosts
• Open source

Cons

• Early-stage project with limited public documentation
• Terminal-centric interface has a learning curve for new users
• Status accuracy depends on job-detection heuristics rather than a universal standard
• Compatibility with every agent CLI is not documented
• Little public evidence of large-scale adoption or benchmarking