HN 표시: TUI 에이전트 멀티플렉서인 Dux

Your AI agents deserve a proper office. dux (pronounced "dooks") is a terminal UI that lets you run multiple AI coding agents side by side, each in its own git worktree, with full companion terminals, macros, commit generation, and a command palette that knows more tricks than you do. No protocol layers. No adapters. No JSON-RPC. Just real CLIs running in real terminals. Most AI coding tools give you one agent in one directory. dux gives you unlimited agents across unlimited worktrees, all visible at once. Spawn five agents on five branches and let them work in parallel. Fork a session to try a different approach without losing the original. Open companion terminals next to your agents for builds, tests, or just poking around. Every agent runs through a PTY, the same pseudo-terminal your shell uses. That means the CLI tool (Claude, Codex, Gemini, OpenCode, or literally anything else) runs exactly like it would in your regular terminal. Your MCP servers, hooks, skills, slash commands, and permission dialogs all work. We don't mess with your setup. Homebrew: brew install patrickdappollonio/tap/dux Shell: curl -sSfL https://github.com/patrickdappollonio/dux/releases/latest/download/install.sh | bash By default, the script installs to ~/.local/bin if it exists and is in your PATH , otherwise /usr/local/bin . You can override the install directory or pin a specific version: # Custom install directory curl -sSfL https://github.com/patrickdappollonio/dux/releases/latest/download/install.sh | DUX_INSTALL_DIR=~/.bin bash # Specific version curl -sSfL https://github.com/patrickdappollonio/dux/releases/latest/download/install.sh | DUX_VERSION=v0.1.0 bash Binary download: Grab the latest release for your platform from the Releases page. Extract it, drop the dux binary somewhere on your PATH , and run it. On first launch, dux creates a fully commented config file. That file is the documentation. git — dux is built around git worktrees, so git is non-negotiable. If it's not on your PATH, dux won't get very far.gh CLI (optional) — authenticate it with your GitHub account and dux can pull PR statuses, check details, and show them right in the interface. Not required, but you'll miss it once you've tried it. dux organizes work around projects (git repos) and agents (worktree sessions). When you create an agent, dux branches off a new git worktree so the agent has its own isolated copy of the code. No conflicts with your main checkout, no stepping on other agents' changes. The interface has three panes: - Left: your projects and agent sessions - Center: the agent's live terminal output (or a file diff) - Right: changed files, staging, and diffs Tab between panes. Resize them with keyboard or mouse. Collapse the sidebar or git pane when you want more room. Go fullscreen with interactive mode. It's your layout. Any terminal command can be a provider. The four defaults (Claude, Codex, Gemini, and OpenCode) are pre-configured, but adding your own is a config-only change: [providers.my-agent] command = "my-cool-agent" args = ["--some-flag"] resume_args = ["--continue"] Set resume_args and dux can reconnect to detached or crashed sessions. Omit it if your CLI doesn't support resuming; dux will just relaunch it. Cycle through providers on the fly with a single keypress, or set a default per-project. Tired of typing the same prompt over and over? Turn it into a macro. Macros are reusable text snippets you trigger from a quick-select bar. Search by name, hit enter, and the text gets pasted into the active pane. [macros] "Review" = { text = "review this code for bugs and security issues", surface = "agent" } "Build" = { text = "cargo build --release 2>&1", surface = "terminal" } "Ship it" = { text = "run all tests, fix failures, then commit", surface = "agent" } Each macro can be scoped to the agent pane, the companion terminal, or both. The right pane is a full git staging area. Stage and unstage files, view syntax-highlighted diffs, write commit messages, push, and pull, all without leaving dux. AI commit messages: Stage your changes, hit a key, and dux sends the diff to your provider in oneshot mode. It drafts a commit message using Conventional Commits, you tweak it (or don't), and commit. The prompt is fully customizable per-project. PR tracking: With the gh CLI installed, dux tracks pull requests for your agent branches and shows status pills right in the interface. Each agent gets its own companion terminal: a separate shell session in the same worktree. Use it for builds, tests, git operations, or anything else you'd normally do in a terminal. You can spawn multiple companion terminals per agent. See an agent going down the wrong path? Fork it. dux creates a new worktree with the current files copied over so you can try a different approach without losing the original session. It's branching, but for your AI conversations. Press the palette key and you get fuzzy-searchable access to every action in dux, including features that don't have dedicated keybindings. Sort agents, toggle UI elements, open the resource monitor, rename sessions, edit macros, and more. If you forget a keybinding, just open the palette. The config file at ~/.config/dux/config.toml (Linux) or ~/.dux/config.toml (macOS) is exhaustively commented. Every setting is explained inline, so you should never need to leave the file to understand an option. Every keybinding is rebindable. Every pane width, scrollback limit, and default provider is configurable. dux config path # Print the config file path dux config diff # Show what you've changed from defaults dux config diff --raw # Unified diff against the default config dux config reset # Remove config and logs (keeps agents) dux config reset --all # Full factory reset dux config regenerate # Preview a fresh default config Override the config directory with the DUX_HOME environment variable. All keybindings live in the [keys] section of the config. Key format supports single characters ("j" ), special names ("enter" , "pageup" , "shift-tab" ), and modifier combos ("ctrl-d" , "ctrl-p" ). Each action takes an array of key combos: [keys] quit = ["ctrl-q"] open_palette = ["ctrl-k"] Press ? in the app for the full keybinding reference. The help overlay is the authoritative source. This README intentionally doesn't list individual bindings because they're yours to change. Logs go to dux.log in the config directory. Control the level in your config: [logging] level = "info" # "error", "info", or "debug" path = "dux.log" # relative to config dir, or use an absolute path