Your MRs. Your worktrees. Your agents. One dashboard.

One of the lovely things about AI now is I have both the time and the resources to build hyper specific tools to my workflows. Pertmux is exactly that. It is designed to fit into my workflows around neovim, tmux and opencode.

Specifically, since the rise of terminal coding agents I have found myself juggling multiple workflows, worktrees and more MRs than ever before. I found myself checking multiple "dashboards" - MR dashboards in github/gitlab. Jumping between various tmux sessions, and list and switching between a multitude of worktrees. Agents would sit idle, MRs would need rebasing and I would miss these opportunities for active work to be done whilst I hyperfocused on whatever my main task is at the time.

Now that we can delegate much of this "meta-maintenance" work for managing work (rebasing MRs, fixing lint issues etc) to AI. We just need a better workflow and dashboard to manage all this in one place. This was the goal of pertmux. There are other solutions out there, all of which great (I was using workmux before building this!), but none quite worked for me and my specific workflows.

I write this all as a disclaimer - I built this tool for myself. Any generic'ness and customisability is very much an after thought. Therefore whilst this tool might be useful to you, I encourage you to fork and modify this to your OWN workflows, or better still use this as inspiration to build your own tools for your own workflows! This is the age of agents, the `agents.md` file is there to quickly onboard agents so you can customise this to your hearts content.