nightmux

nightmux is an open-source, MIT-licensed Python tool that drives terminal AI coding agents such as Claude Code, Codex, Gemini, opencode, Cursor, Amp, Goose and Qwen Code inside tmux sessions. You control them from Telegram or a phone dashboard, and when an agent hits its usage limit the queue waits and resumes when the window resets, or hands the work to another agent. The latest release listed is v1.3.0.

What It Is

nightmux is a self-hosted agent-control layer that sits on top of tmux sessions on your own machine. Each project maps to a Telegram forum topic (or a chat in the dashboard) bound to a tmux session. Text, photos, files and voice notes you send are typed into the agent's prompt, and output and approval requests come back as messages with tap buttons. The README describes it as a single stdlib-only Python file with no dependencies, and says no relay sees your code.

Overnight workflow

The core job is keeping work moving unattended. nightmux reads the reset time of a usage limit, holds queued prompts, and re-sends the interrupted turn when the window reopens. Other documented commands cover scheduled starts (!at, !every), step queues (!shift, !plan), and !goal, which runs a check such as tests after every turn and sends failures back to the agent until it passes. A morning briefing summarizes what was done overnight.

Multiple agents and visibility

A topic can hold several agents, with commands for failover, consulting, pair reviews and racing two agents in separate worktrees. Usage tracking covers context percentage, limit windows, cost and stats. A dashboard, chat PWA, pixel-art office view and an Android app provide visibility, and a demo mode runs without a bot or keys.

Setup path and security model

Install is via a one-line installer, pipx, a git clone, or Docker, and setup handles the Telegram bot, allowlist, Claude Code hooks and a systemd or launchd service. Requirements listed are Python 3.8+, tmux and a terminal coding agent. The README warns that the bot token is effectively a shell on your machine, so allow_users is the key safeguard; the dashboard binds to 127.0.0.1 by default and risky approvals such as rm -rf or git push are not auto-approved.