You might like what I'm working on at DBD: https://deepbluedynamics.com/nemesis
replyJust adding a menu this morning to allow re-attaching and session management.
Yes, looks fun .. thanks for sharing. A lot of competition in this space though, of course ..
replyI do a similar thing where the agent runs in a Docker container and I talk to it with Telegram. It has GitHub CLI access but only with a very restricted PAT. No bind mounts. Jira is pretty clever, though I'm not feeling enough pain with just Telegram to want to try switching at this point.
replyI have multiple relatively well-established Jira projects I've been able to add agents to, and also clone/use as a template for new agent-only projects which give me another kanban to manage, pretty comfortably ..
replyThe big thing about my Jira use besides the fact that its a historical tool into which I've integrated agents, is that managing agents through Jira's custom workflows is really, really cool. You can actually do any of the old workflows with agents - they'll just do it. Finally, effective waterfall! ;) *Just kidding, I've always been able to do waterfall properly...
Why are you using Jira and not GitHub issues?
replyOne thing that is vital to managing agents this way, is the ability to easily create and use workflows, which can be easily kanban'ed. This is where I find Jira very comfortable - plus, I am already accustomed to managing Jira with both a workflow-driven Kanban, and jira-cli, the command-line interface.
replySo actually, firing off commands with jira-cli to get flows started by multiple agents watching their issues and putting their work in issue threads, is quite a nice interface .. and compatible with the other human-powered projects I'm managing this way, also.