← All tools

nomograph-ai/muxr

Popularity 65 Updated AI & Agents

Harness session multiplexer for AI coding workflows. Mirror of gitlab.com/nomograph/muxr.

githubauto-collected

Installation

A directly usable install command is not verified yet. Check the project documentation or releases.

muxr

Session multiplexer for AI coding workflows. Owns the address <repo/<campaign across tmux, the filesystem, and your AI runtime, so a rename or move stays coherent in all three.

What it is

muxr is a tmux + AI runtime session manager. Sessions live as typed records on disk; tmux state and the runtime command stay in lockstep with that record. muxr save snapshots; muxr restore brings everything back.

The problem

You work across multiple projects. Each one needs its own terminal session with the right working directory and the right tool running. You open tabs, cd around, lose track of what is where. When you reboot, everything is gone.

muxr organizes tmux sessions into repos (local directory trees) and remotes (GCE instances). Each session knows where it lives and what tool to run. muxr save snapshots everything. muxr restore brings it back.

Install

cargo install nomograph-muxr

Pre-built binaries for macOS arm64 and Linux amd64 are available in releases.

Quick start

muxr init                                # create config
muxr work                                # open the work repo switchboard
muxr work retrieval-precision            # open work/retrieval-precision campaign session
muxr switch                              # interactive chooser to jump or launch
muxr save                                # snapshot before reboot
muxr restore                             # bring everything back

Sessions are addressed as <repo/<campaign -- two levels. Campaigns are kebab-case and name the initiative (e.g. cicd-stub-fix, retrieval-precision); they are not date-stamped. The per-repo switchboard is a singleton at <repo/switchboard. When a topic crystallizes inside a broad campaign, muxr shard <new spins it out into a sibling campaign instead of adding a third name level.

Config

One file: ~/.config/muxr/config.toml

default_tool = "claude"

[repos.work]
dir = "~/projects/work"
color = "#7aa2f7"

[repos.work.launch]
append_system_prompt_file = "HARNESS.md"   # optional repo-level prompt
add_dirs = ["~/docs/shared"]               # optional base --add-dir paths

[repos.personal]
dir = "~/projects/personal"

[remotes.lab] project = "my-gce-project" zone = "us-central1-a" user = "deploy" color = "#d29922"

connect = "mosh" # default; set to "ssh" for gcloud compute ssh