AMUX vs Kelet

AMUX is an open-source agent multiplexer that lets you run dozens of Claude Code (or other terminal AI coding agents) simultaneously, all managed from a single web dashboard — no complicated setup required. Built by the team at Mixpeek, it requires only Python 3 and tmux, with the entire server delivered as a single ~23,000-line Python file with embedded HTML/CSS/JS. The standout features are a self-healing watchdog that auto-compacts context when it drops below 20% and restarts stuck sessions, a SQLite-backed kanban board where agents atomically claim tasks to prevent duplicate work, and a REST API injected at startup that allows agents to coordinate with each other via simple curl calls. There's even a mobile PWA with offline support via Background Sync so you can monitor your agent army from your phone. In the "agentmaxxing" era, AMUX is the most complete open-source solution for running parallel AI coding agents unattended. Rather than babysitting one agent, you dispatch 5–20 agents to isolated worktrees and check back in as a reviewer. The MIT + Commons Clause license means it's free to self-host.

Kelet is a root-cause analysis agent for LLM applications that goes beyond trace visualization. Where most observability tools stop at showing you what happened, Kelet automatically reads your traces, cross-references failure patterns across thousands of sessions — thumbs-down ratings, abandoned conversations, LLM-judge flags — generates root cause hypotheses, and produces targeted prompt patches to address them. The workflow is: connect your traces (LangSmith, Langfuse, or direct API), let Kelet ingest your failure signals, and receive a prioritized list of failure clusters with explanations and draft prompt fixes. SOC 2 Type II certified, read-only access to traces — nothing is mutated. The indie team positions it as the missing "closing of the loop" in LLM observability: most teams can detect failures but have no systematic path from detection to fix. The HN thread surfaced a real pain point: teams know their chatbot is failing somewhere, but diagnosing which prompts, tools, or routing decisions are responsible requires manual trace archaeology. Kelet automates that archaeology and produces actionable output, not just dashboards.