Flowmux banner
flowmux-ai flowmux-ai

Flowmux

Productivity community

Description

flowmux — Agent Workflow Multiplexer Terminal. Go with the agents' flow.

Installation

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

README

flowmux

![icon](resources/icons/flowmux-180.png)

**Agent Workflow Multiplexer Terminal** — *Go with the agents' flow.*

[Website](https://flowmux.org/) · [Latest release](https://github.com/flowmux-ai/flowmux/releases/latest)

A terminal for AI agent workflows, browser control, and task signals.

flowmux is a Linux/GTK4 terminal for AI coding agents. The terminal pane uses the system VTE widget for terminal emulation, flowmux-owned PTYs, and GTK integration. Supported on Ubuntu 24.04 and later.

Unofficial GPL-3.0-or-later reimplementation inspired by [cmux](https://cmux.com/ko), a macOS/AppKit app. Not affiliated with cmux.

Install (Ubuntu 24.04+, amd64)

curl -fsSL https://flowmux.org/install.sh | sh

Uninstall the release package with `sudo apt remove flowmux`.

Control internal browser

A WebKitGTK 6.0 browser tab lives next to terminal tabs in the same pane tree. The clip shows an AI agent driving the page over flowmux's IPC socket — snapshot the DOM, click, type, read state back — with no system Chromium and no separate driver.

![video](resources/screenshot/video_control_browser.gif)

AI Agent notification (Claude, Codex, OpenCode, Gemini, Antigravity)

`flowmux fix` adds lifecycle hooks to Claude Code, Codex, OpenCode, Gemini, and Antigravity. FlowMux keeps session start/end separate from turn working/waiting/completion, then surfaces attention and completion as native desktop notifications — routed to the workspace that fired them, suppressed while that surface is focused, and isolated per window.

Claude's `PermissionRequest` has no tool-use ID, so FlowMux keeps a conservative permission marker for the whole model-call batch and clears it at the matching `PostToolBatch` boundary. Explicit input tools are still correlated by their tool-use IDs. Codex permission waits are scoped to the reported root or child turn and are cleared only