nhtera

OxiMux — Design skill for Claude Code

Design community

A Rust-native, multi-agent development cockpit for macOS — spawn isolated worktrees, run CLI coding agents in parallel, and review every change through a GitLens-grade Git UX.

How to install OxiMux

This entry records only its repository, not the path inside it, so there is no exact command to give. Open nhtera/OxiMux and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What OxiMux does

A Rust-native, multi-agent development cockpit for macOS — spawn isolated worktrees, run CLI coding agents in parallel, and review every change through a GitLens-grade Git UX.

Alternatives in Design

Frontend Design — Create distinctive, production-grade frontend interfaces with high design quality 94.1k ★
CloudCLI — 8,400+ Free open-source web/mobile UI for Claude Code, Cursor CLI, and Codex 8.7k ★
Grade — Generate a shareable HTML "Design Report Card" — letter grade, 8 dimensions, evidence (palette, type, rhythm) 3.6k ★

README

OxiMux

A Rust-native, multi-agent development cockpit for macOS. Open a repo → spawn isolated worktrees → run CLI coding agents (Claude Code, Codex, Pi, omp) in parallel → review every change through a GitLens-grade Git UX.

Stack: Rust 1.95 (edition 2024) + GPUI + `longbridge/gpui-component` + SQLite + Tokio
Status: Working cockpit, in active development. Dogfoodable for day-to-day repo work; pre-1.0, so expect rough edges.
Platform: macOS-only in v1 (13.0+).

![The OxiMux cockpit — projects and agents in the rail, agent chat tabs in the center, Git changes and commit graph on the right](apps/landing/src/assets/shots/cockpit.png)

![Claude Code and Codex running side by side in an isolated worktree, with the Git panel tracking changes](apps/landing/src/assets/shots/worktrees.png)

Quick start

# Build the PTY relay daemon first — the app resolves it as a sibling of
# its own binary, and without it terminals fall back to in-process PTYs
# that don't survive a relaunch.
cargo build -p oximux-relay --release

# Build + run the shell (release ~slow first time due to GPUI compile)
cargo run -p oximux-app --release

# Or produce an .app bundle in dist/ (bundles oximux + oximux-relay)
./scripts/bundle-macos.sh
open dist/OxiMux.app

Building on Windows

macOS is still the shipping target; the Windows port lives on `feat/windows`. What it leaves behind is recorded in [`docs/windows-port-exclusions.md`](docs/windows-port-exclusions.md).

# Produce dist/OxiMux — the app plus every sibling it resolves at runtime
# (relay daemon, screen-control hook, ripgrep, dictation DLLs).
./scripts/bundle-windows.ps1
./dist/OxiMux/oximux.exe

Running straight out of `target/` works too, but only the bundle carries `oximux-screen-gate.exe`, and without it agent chats run unpoliced. See [`docs/windows-packaging.md`](docs/windows-packaging.md).

Beyond the Rust toolchain and the MSVC build