Get This Tool
Kmux
Pricing
- Model
- Free
Summary
Running three AI coding agents on the same repo means environment collisions, tangled git states, and no single place to know what any of them spent on tokens. kmux is a terminal workspace built to fix that specific mess.
kmux organizes parallel Claude Code, Codex CLI, and Antigravity CLI sessions into a keyboard-driven terminal dashboard on macOS and Linux. Each agent gets its own isolated git worktree automatically, so two agents editing the same codebase stop stepping on each other. A built-in dashboard surfaces API token usage and spend across all sessions in one view — without opening a browser or switching tools. Session history is indexed locally, so you can resume a previous agent run rather than starting cold. The ceiling appears when your workflow reaches outside the terminal: there is no API, no webhook surface, and no integration path for CI pipelines or remote orchestration.
Bottom line: Pick kmux when you are juggling two or three local AI coding agents and need isolation and cost visibility without standing up infrastructure — but plan a different approach the moment you need to trigger or monitor agents from CI or a remote system.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Automatic git worktree creation per agent session, so two agents working the same repository never produce conflicting working-tree state that you have to untangle by hand.
- Centralized API token and spend dashboard across all running sessions, so a runaway agent burning through quota surfaces immediately instead of showing up on your provider invoice.
- Local session history indexing lets you resume a previous agent run from where it stopped, so context is not lost when a session crashes or you close the terminal.
- MIT license with self-hosted deployment, so there is no vendor controlling your data, no usage caps imposed by a SaaS tier, and no cost that scales with your team size.
- Keyboard-centric navigation across all sessions, so context-switching between agents does not require a mouse or a separate window manager.
Cons
Sign in to edit- No API, webhook, or programmatic interface exists. Any team that wants to trigger agent sessions from a CI pipeline, monitor session state from an external dashboard, or integrate kmux into a broader automation chain hits a hard wall — and moves to a solution like a custom tmux setup with scripted session management or a platform that exposes an API.
- Support is limited to Claude Code, Codex CLI, and Antigravity CLI as named integrations. Teams running other agent tooling — or custom agent scripts — have no documented integration path and no guarantee the worktree and session management will behave correctly.
- macOS and Linux only. Teams with Windows developers in the workflow cannot use kmux as a shared standard and end up maintaining separate local setups per OS, which defeats the consistency the tool is meant to provide.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- macOS, Linux
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-15T18:31:36.502Z
Best For
Who it's for
- Developers using Claude Code, Codex CLI, or Antigravity CLI
- Managing parallel agent workflows on the same repository
- Tracking API costs and session history centrally
What it does well
- Running multiple AI coding agents in parallel without environment conflicts
- Monitoring API token usage and spend across agents in one view
- Resuming previous agent sessions from indexed local history
- Isolating agent work via automatic git worktrees
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare Kmux
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Kmux free?
- Yes — Kmux is fully free to use. There is no paid tier.
- Is Kmux open source?
- Yes. Kmux is open source.
- Can I self-host Kmux?
- Yes. Kmux supports self-hosting on your own infrastructure.
- What platforms does Kmux support?
- Kmux is available on: macOS, Linux.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
kmux is an open-source, self-hosted terminal workspace for developers running multiple AI coding agents — specifically Claude Code, Codex CLI, and Antigravity CLI — in parallel on macOS and Linux. The core workflow is keyboard-centric: sessions are launched and navigated without leaving the terminal, each agent runs in its own pane, and the tool manages the underlying git worktree creation automatically so agents have isolated working directories from the start.
The differentiating feature is the combination of automatic git worktrees and a centralized API usage dashboard. Most developers tracking parallel agent spend are either reading provider dashboards per-tool or doing mental math. kmux surfaces token usage and cost across all active sessions in one view inside the terminal, which means you catch a runaway agent before the bill does.
kmux fits solo developers and small teams who run AI coding sessions locally and want structure without overhead. It breaks when the workflow moves off the local machine: there is no API surface, no webhook support, and no documented path for connecting kmux to CI systems, remote servers, or other tooling. Teams that need to trigger or monitor agent sessions programmatically will find nothing to integrate against and will move to a solution with an API or a process management layer they control.
The project is MIT-licensed with no paid tiers. It ships as a monorepo with a desktop app directory alongside the terminal packages, though the primary documented use case is the terminal workspace. End-to-end tests are present in the repository, and the project includes multilingual READMEs, a code of conduct, and a security policy — markers of a project structured for external contribution rather than a personal script.