I'm so married to my existing tmux workflows and layout that I'm not sure whether I'd ever feel open to trying out something like this. At the same time, orchestrating multiple agents with native tmux and git worktree does feel cumbersome.
thijsverreck 9 minutes ago [-]
if you want you can file an issue with your current workflow? happy to see if we can do a PR to support this natively in tmux-ide
I love cmux! ironically you can use tmux-ide within cmux. The idea is to make it an agent development environment that's great when ran on a remote machine :).
cyrusradfar 15 minutes ago [-]
Congrats on getting this out. What was the most surprising part of the build?
thijsverreck 11 minutes ago [-]
most surprising was that something this lightweight made such a big impact on my productivity. its really nice to have persistent Claude teams on my remote machines that I can always access no matter what.
theturtletalks 2 hours ago [-]
I'm also trying to build something similar for agent orchestration where one terminal is controlling multiple terminals. I tried using tmux but it's very good at sending the initial text to the tmux sessions, but I've not been able to get an agent to have a proper back and forth controlling multiple tmux sessions. I know we can use send-keys, but reading the session or knowing when that session is complete is kind of up in the air. And then if the main orchestrator terminal has checked all the sessions to see if they're actually working and doing things, the main session kind of stop so I've kind of been thinking about a cron that periodically checks in and nudges it to check the sessions again. Are they still working? Do they need more guidance? Essentially having one terminal control others, but having that back and forth with the terminals has been pretty challenging to achieve. Have you gotten anywhere with this?
SparkyMcUnicorn 48 minutes ago [-]
It sounds like maybe you haven't seen agent teams mode, which this project is using.
Looks like a great implementation. I want to question the basic user story, which seems to be: "I am a software developer who wants to improve productivity by running multiple simultaneous agents that are roughly isomorphic to a human software developer team."
I am burning a lot of tokens every day at work and on personal projects. It's helpful. I generally work in tmux with github copilot in one pane, and a few other terminal panes showing tests and current diff.
I find it really important to avoid the temptation to multi-task by running multiple agents. For quite varied tasks, productivity gains from multi-tasking have proven to be illusory. Why would it be different with writing software?
https://code.claude.com/docs/en/agent-teams
I am burning a lot of tokens every day at work and on personal projects. It's helpful. I generally work in tmux with github copilot in one pane, and a few other terminal panes showing tests and current diff.
I find it really important to avoid the temptation to multi-task by running multiple agents. For quite varied tasks, productivity gains from multi-tasking have proven to be illusory. Why would it be different with writing software?
https://en.wikipedia.org/wiki/Human_multitasking