← ClaudeAtlas

amuxlisted

Run background tasks, long-running processes, servers, and anything you'd use tmux for. Named panels persist across commands. Use for dev servers, Electron apps, build watchers, tailing logs, running test suites, or any process that needs to keep running while you do other work.
Zero-inadequateness813/amux · ★ 0 · Web & Frontend · score 62
Install: claude install-skill Zero-inadequateness813/amux
# amux — background panels for agents Named tmux panels for long-running processes. Panels are created on first use, tiled within sessions grouped by project root. Architecture: one global tmux server (separate from your tmux) → sessions (one per project, detected via .git) → panels (named panes, dwm-style tiling). ## The run → tail workflow This is the primary pattern. Start with `amux_shell`, which streams output for a short timeout (default 5s). If it finishes, you get SUCCESS or FAIL. If it times out, the output tells you exactly how to continue: ``` ⏳ timeout 5s — continue with: amux_tail(name: "tests", follow: true, offset: 4820) ``` Call `amux_tail` with that offset to resume exactly where `amux_shell` stopped. No output is lost or duplicated. If `amux_tail` also times out, it prints another continuation hint — keep chaining until done. ### Quick command (finishes in time) ``` amux_shell(name: "test", command: "npm test") → ... test output ... → SUCCESS ``` ### Long command (timeout → continue) ``` amux_shell(name: "test", command: "npm test") → ... partial output ... → ⏳ timeout 5s — continue with: → amux_tail(name: "test", follow: true, offset: 4820) amux_tail(name: "test", follow: true, offset: 4820) → ... remaining output ... → SUCCESS ``` ### Very long command (chain multiple tails) ``` amux_shell(name: "build", command: "make all", timeout: 30) → ⏳ timeout 30s — continue with: → amux_tail(name: "build", follow: true, offset: 52000) amux_tail(name