amux vs codeg
AI coding agent coordination tools compared
amux and codeg both help developers coordinate multiple AI coding agents. amux centers on tmux-managed workers, a shared task board, and recovery, while codeg provides an ACP-based workspace for agent sessions, code changes, and repository workflows.
amux: Coordinate Parallel AI Coding Agents with Rust and tmux
amux is a Rust control plane that runs Claude Code, Codex, and Gemini CLI agents in parallel through tmux. It gives developers a shared task board, agent messaging, schedules, and recovery tools, with a dashboard for macOS, Linux, and mobile access.
codeg: Coordinate AI Coding Agents with Agent Client Protocol
Codeg is a collaborative workspace for running and coordinating AI coding agents through the Agent Client Protocol. It brings agent conversations, sessions, code changes, and tasks into one experience across desktop, self-hosted server, Docker, and mobile.
| amux | codeg | |
|---|---|---|
| Language | Rust | Rust |
| License | — | Apache-2.0 |
| Stars | 547 | 4k |
| Forks | 69 | 518 |
| Last analyzed | Oct 26, 2026 | Oct 19, 2026 |
Key differences
- amux manages Claude Code, Codex, and Gemini CLI agents through tmux; codeg connects built-in and custom agents through the Agent Client Protocol.
- amux emphasizes atomic task claiming, agent messaging, schedules, and session recovery; codeg combines conversations with live diffs, files, terminals, an editor, and Git hosting workflows.
- amux offers a browser dashboard and companion apps for Mac, iPhone, and iPad; codeg supports desktop, self-hosted server, Docker, iOS, Android, and messaging integrations.
- amux uses local-first SQLite storage with optional amux Cloud; codeg describes sessions and project operations as local-first and supports token-authenticated server access.
- amux lists MIT plus Commons Clause in its README, while repository metadata reports NOASSERTION; codeg lists Apache-2.0.
- Both projects use Rust and are active, but codeg has more reported stars and forks; contribution is heavily concentrated in one contributor for each.
Choose amux if you…
- need tmux-based coordination for parallel coding agents.
- want a shared task board, agent messaging, scheduled runs, or worker recovery.
- prefer a local-first dashboard with an optional hosted service and Mac companion app.
Choose codeg if you…
- want an ACP-based workspace that brings agent sessions and code changes together.
- need integrations such as Docker, Android, messaging platforms, or a CLI for scripts and CI.
- want repository workflows for issues, pull requests, checks, and merges across supported Git platforms.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.