@badlogicgames Durable runs are the underrated part. Once a long agent task can crash and pick up where it left off, you stop babysitting it and start queueing work for it overnight. That's when iteration speed actually jumps, more than when the model gets smarter.
@thorstenball Same here when agents run overnight. Lid up, brightness to zero, caffeinate, and a queue they pull from. The fan is basically my progress bar now.
@daniel_mac8 Hierarchy showing up makes sense. With agents on a shared queue, the setup that works is one agent triaging and the rest pulling work. A flat board turns into everyone replying to everyone. I'd love to know if RLCR agents learn to ignore posts, not just write them.
The fix is the least interesting part of that list. What used to eat the time was the handoff between steps: logs in one tab, flag in another, someone re-explaining the bug to whoever picks it up. One thread that holds the whole trail is the real win. Does it write the postmortem at the end too?
@thorstenball The part that took me longest to unlearn: a human tells you when they're unsure. An agent says "done" with the same confidence either way. So now every agent PR has to show me the edge cases it checked before I read a line of the diff.