tmux VS Tmuxinator

The hard part is the hand-off. I tried three using a shared tmux session and a filesystem via handoff file, and with an ACP (Agent Communication Protocol):

tmux is still hard to beat when you need persistent terminal sessions, panes, and project workspaces.

This tutorial provides a practical introduction to TMUX and how you can use tmuxinator to easily set up terminal dashboards with logs and shell sessions for your docker compose projects.

tmux official GitHub repository

tmux/tmux

Combining tmux with Ghostty unlocks Agent Teams split-pane mode, plus:

tmux GitHub

tmux is the terminal multiplexer — it lets you run persistent, multi-pane terminal sessions that survive disconnects. If you close your laptop and come back, your tmux sessions are still running.

This tutorial provides a practical introduction to TMUX and how you can use tmuxinator to easily set up terminal dashboards with logs and shell sessions for your docker compose projects.

The next step will be a tool that can help us achieve fast bootstrapping of the projects (sessions), it can be either teamocil or tmuxinator, these are the most popular ones and in this tutorial, I will use teamocil. Those tools allow you to write a configuration for a specific session and run this session with many processes and windows in one click.

Well, I now use tmux and tmuxinator. I have had many failed tmux attempts over the years, but I'm firmly bedded in now.

I once bought a 32 core ThreadRipper and tried to get along with using a cheap £200 Windows 10 laptop to remote into the threadripper while in coffee shops and use the ThreadRipper to do my work.

The £200 Windows 10 laptop wasn't powerful enough, it was too laggy. Even on Wifi.

I love the idea of the X11 protocol. And I still love the idea of a web desktop. Something that is supremely well integrated and allows me to move workloads between client and server seamlessly. This idea I really like. The ability to outsource computation and storage seamlessly. A process can be moved between machines seamlessly.

This could be modelled in Javascript and promises that can be sent around. Microservices in the desktop environment.

I looked at tools that would bring up tmux sessions with everything preloaded. (https://github.com/tmuxinator/tmuxinator)

ScrapScript has very good ideas in this area of distributing dependencies and storage. (https://scrapscript.org/) There is also val town.

I never use KDE Plasma widgets or the sidebar widgets that Mac provided.

There is so many exciting ideas that could be tried out but I worry they're all too big ideas to be implemented.

tmuxinator

I use https://github.com/tmuxinator/tmuxinator for my workspaces. Doesn't save ad-hoc layouts, but usually I find one layout that works per project, then create a tmuxinator config for it, so after reboot, it's a short "tmuxinator start $my-project" away to get back to how I want it to be.

you might be interested in: https://github.com/tmuxinator/tmuxinator

I’ve become a huge fan of tmuxinator. Incredible tool for defining templates for tmux.

https://github.com/tmuxinator/tmuxinator