15:I[981,["658","static/chunks/658-a698693f56d0116a.js","183","static/chunks/183-6beeeb801c274aaa.js","474","static/chunks/app/%5Btype%5D/layout-e8e83705b5c8d3b7.js"],"Posts"] 16:T70a,Hey HN!

Since terminal coding agents took over my workflow, I've been juggling more worktrees and MRs than ever — constantly switching between GitLab/GitHub dashboards, tmux sessions, and git worktrees. Agents would sit idle, MRs needed rebasing, and I'd miss it all while focused on my main task.

Hence I built Pertmux. It's a Rust TUI (shout out to ratatui — http://ratatui.rs) that links everything together in one dashboard: MRs from GitHub/GitLab, git worktrees, tmux panes, and coding agents. Select an MR and you see its linked branch, worktree, pipeline status dots, and which agent is working on it. Create and manage worktrees, jump straight into tmux panes, or send commands to agents (rebase, fix CI) — all without leaving the dashboard. It runs as a background daemon so the data is always fresh, and can pop up as a tmux overlay so it's one keybind away.

Built for my own workflow around neovim + tmux + opencode. The architecture is pluggable (traits for forges and agents), and there's an AGENTS.md to onboard coding agents for customization. I'd encourage you to fork, open Issues/MRs and do what you want. I think we're all better off building hyper specific tools to fit our own needs since it's easier than ever before to do, and I hope Pertmux at least provides you a great jumping off point.

Heavily inspired by workmux so shout out to them! https://github.com/raine/workmux Worktree management is based upon the fantastic CLI worktrunk: https://worktrunk.dev/

Ask HN: Okara's new AI CMO: Will this solve the marketing problem?

Comments