11–20 of 115 posts
Tried this for a couple days, but conductor.build is way better IME. Running _in_ the terminal is a flex, but doesn't actually bring any advantage.
Tried this for a couple days, but conductor.build is way better IME. Running _in_ the terminal is a flex, but doesn't actually bring any advantage.
Running in the terminal means I can access it via ssh on my phone (& tailscale). Do any of the other solutions let you do this?
does it support a setup where each agent can be in a different SSH session? or must they all run in the same place. it seems to support running a remote herdr over SSH but unclear if it can add remote agents (each agent has its own sandbox where its installed and you first SSH into it and then start the agent there)
Same question. I usually have one local clause orchestrating multiple remote Claude in different tmux . And then another orchester and remote vm worker sin tmux for another repo etc... It gets a bit hard to keep the overview but I don't want to give up my parallelism, your too might help
Earlier quoted context omitted.
Same question. I usually have one local clause orchestrating multiple remote Claude in different tmux . And then another orchester and remote vm worker sin tmux for another repo etc... It gets a bit hard to keep the overview but I don't want to give up my parallelism, your too might help
Interesting, how is this orchestration set up?
nice, not dissimilar to what i built for https://github.com/storozhenko98/beehive
Earlier quoted context omitted.
How would you know if a tab that isn't frontmost is waiting for input or complete or whatever?
You use an agentic harness which terminates with bell character[0]. This lights up tmux, clearly indicating that it's done. [0]: https://en.wikipedia.org/wiki/Bell_character
Ctrl+B is so hardwired in my fingers for scrolling back one screen that there's no way I'm remapping that one in vim itself. So then you have to remap that in your terminal multiplexer, while at the same time there's a bunch of people saying never change the leader key...
Curious what vim users especially do about this?
Earlier quoted context omitted.
You use an agentic harness which terminates with bell character[0]. This lights up tmux, clearly indicating that it's done. [0]: https://en.wikipedia.org/wiki/Bell_character
Does this mean adding instructions to AGENTS.md saying to end everything with the bell character? Or do harnesses have this in their settings somewhere?
How do people use terminal multiplexers together with vim? Ctrl+B is so hardwired in my fingers for scrolling back one screen that there's no way I'm remapping that one in vim itself. So then you have to remap that in your terminal multiplexer, while at the same time there's a bunch of people saying never change the leader key... Curious what vim users especially do about this?