#tmux
8
2026-10-05
yanglited/tmux-scrollable
A
Scrollable tiling for tmux, like niri and PaperWM: new columns scroll in from the right instead of squeezing your panes
2026-10-08
Show HN: Puppet Master – Manage coding agents at scale
未评级
As I started to use `claude` and `codex` more it became too hard to manage all the sessions across all my tmux panes and sessions, so I built Puppet Master. I see now there is quite a lot out there now for managing agents to write software, but a) I started working on this before a lot of them, and b) there are things in Puppet Master that just don't exist all in one product. For me I'd say the highlights are: 1) Web instead of terminal -- it's just a richer interface 2) iOS app so I can keep working on things from anywhere 3) Local + Remote workers (heterogeneous fleet), I work on things that are cross-platform and PM lets agents spawn across the fleet depending on workload needs. 4) Connections - first-class support for integrating MCP and REST API (ala OpenAPI definitions) into your agents. This goes above and beyond what a single harness can do via i.e an MCP integration. PM imports it (scoped to a bucket/project) and associates it to a policy. It lives between the agent and the remote MCP/API and enforces a policy. My normal flow is give full read access to agents and any APIs that do writes, approval needed. PM has native approval UI on web AND mobile so you can give real agency to your agents without being too permissive. 5) Code review interface is nice, 1-1 discussions on comment threads in the review, pretty responsive. 6) Forwards/artifacts allow agents to share static artifacts/html/etc,. OR serve up any dev server. This is proxied so even things on remote workers "just work" and you can access them, securely. GitHub: https://github.com/chrismoos/puppet-master
2026-09-25
Show HN: I measured my tmux statusbar at 15% of a core and replaced the forks
未评级
tmux status-interval 1 had six #() programs for statusbar, on battery that was 15.4% of a core. After digging found fork+exec through sh -c is ~14.6 ms and computing the actual segments was 2.6 ms on my device. Plus had ~1.5k lines of zsh scripts. Now one deamon process, caches in memory, unix socket and one #() for the whole right side. From 153.77 ms/s → 18.43 ms/s. Made that into a tmux plugin. You can try it without installing/configuring: docker run --rm -it lonkarorg/tmux-companion:playground
2026-09-19
Show HN: Lodestar – Read, respond and manage coding agents more naturally
未评级
I was frustrated by having 10 terminal windows open, and I checked a few solutions on how to make this better. They are all nice, but then I realized what I really wanted was something that feels a bit deeper and more intelligent than a "dashboard" of all your agents. For example, I routinely have 3+ agents exploring different frontiers of the same idea. How do I keep them inline? What if I see 3 more promising directions from one of them? How do I tie up all the loose ends? If I see one agent got a brilliant observation, how do I easily spread that to other agents? So I started exploring many ways to connect agents together. That led me to realize that the actual fundamental things are not the agents, but the substance. Understandings, decisions, insights, etc. Can I quickly understand what's said? Can I quickly react to it? Can I quickly find it two days later? Can I quickly share to other agents? When ideas and insights are scattered across agents, can I organize those? Can I easily share with the next new agent? I tried to make optimizations through those angles. Though still far away from my vision, there is enough value that I think it's interesting to share. A few concrete features: - Agents proactively leverage graphs and annotations to explain ideas - You can comment inline on text, docs, html files. React to things right where they are - You can find messages or docs from days, weeks ago by describing what you remembered instead of using exact keywords. Agents can too. - You can organize topics and sessions in hierarchical or graphical structure (automatically). Or ask an agent to do it if you want it in some particular flavor. In those session maps, everything remains clickable and interactive, with real time status too. So you can have an agent to start 10 sessions in the morning, draw their dependencies and relationships, and watch each agent work through their task until everything in the whole map is finished. Add, remove, tweak, or reorganize the tasks as you wish. Anyway, that's a lot of words... I don't expect you to read all that. If you find it interesting enough, give it a try!
2026-09-16
Show HN: Seamless pane navigation across nested tmux sessions over SSH
未评级
Hey, I've got tired of dealing with tmux prefixes so I made a plugin that makes pane switching seamless across SSH/nested tmux boundaries. Now you can just use Alt+↑/↓/←/→ instead of doing mental math calculating the right combination of prefixes to switch panes. Enjoy!