I checked out your project and noticed some interesting parallels with my project (Jailbee, https://jailbee.gisgro.io). Both support parallel development workflows but at different levels: pi-cowboy orchestrates agents in isolated git worktrees where JailBee isolates entire development environments, including Docker, networking and services.
Separating agent orchestration from execution environent provisioning could enable pi-cowboy agent to run inside something like JailBee container instead of just a worktree. What do you think?
Thank you for the feedback. I am working on a plugin system. I've made the coding harnesses and the multiplexer pluggable, but I had not considered this angle. I think it makes sense. When it's ready, would you be interested in writing a plugin for Jailbee and help iron this out? I've created an investigation issue for this: https://github.com/electric-dragon-80000v/pi-cowboy/issues/2...
I checked out your project and noticed some interesting parallels with my project (Jailbee, https://jailbee.gisgro.io). Both support parallel development workflows but at different levels: pi-cowboy orchestrates agents in isolated git worktrees where JailBee isolates entire development environments, including Docker, networking and services.
Separating agent orchestration from execution environent provisioning could enable pi-cowboy agent to run inside something like JailBee container instead of just a worktree. What do you think?
Thank you for the feedback. I am working on a plugin system. I've made the coding harnesses and the multiplexer pluggable, but I had not considered this angle. I think it makes sense. When it's ready, would you be interested in writing a plugin for Jailbee and help iron this out? I've created an investigation issue for this: https://github.com/electric-dragon-80000v/pi-cowboy/issues/2...