Vibepanel

vibepanel

**A web console for running many parallel coding-agent sessions.**

tmux keeps the processes alive. The browser owns everything else: how sessions are grouped into projects, what they are called, which one needs you right now, and what order they appear in.

[](https://github.com/jiangmuran/vibepanel/actions/workflows/check.yml) [](go.mod) [](#requirements) [](LICENSE)

**English** · [简体中文](README.zh-CN.md)


The problem

Run a dozen coding agents at once and a terminal multiplexer gives you a flat strip of tabs called `bash`. You cannot tell which agent is waiting on a confirmation and which is still working without clicking into each one. Tabs belonging to one project are scattered among tabs from five others. None of it is usable from a phone.

That is a task-management problem wearing a terminal costume. vibepanel splits the two apart: **tmux does process persistence, the web UI does organisation.**

What you get

• Sessions that outlive the panel. Every session is a tmux session on a dedicated socket. Restart, upgrade or crash the panel and nothing notices — the processes are children of the tmux server, not of this program.
• A status you can read across the room. working, waiting for you, done. Waiting sorts first and is the loudest thing on screen. States are told to the panel by the agent where a hook is installed, and read from the output stream where it is not.
• Projects, names that stick, and ordering that means something. Rename a session and it stays renamed;