4 ms·
The whole flow of: creating container -> cloning repo -> making change -> test -> send PR is too slow of a loop for me to do anything much useful. It's only g
by asadm 1y ago
The whole flow of:
creating container -> cloning repo -> making change -> test -> send PR
is too slow of a loop for me to do anything much useful. It's only good for trivial "one-shot" stuff.
- lsaferite 1y agoI'd say this method of coding agent interaction is likely a strong contender for integrating coding agents into teams. You start with a really well defined ticket and a good source of relevant documentation for the project then set the agent loose by assigning it a ticket. It does it's thing, maybe asks questions on a group chat or in the ticket, and eventually produces a PR for the ticket. It's the 'interface' behind how a developer interacts with a project already. There's a lot of hand-waving in there and it's not a today or tomorrow thing, but it seems like it's coming fairly soon.
- asadm 1y agothats the premise behind the popular Devin. I don't think it saw any market fit.
- lsaferite 1y agoI think my wording was unclear. I've run into several products doing this or something similar already. I was more trying to say I think this methodology is going to be the most likely winner of how coding agents are integrated into dev teams. There are still a lot of aspects to work out fully, but they are being worked out.
- jmj 1y agoOpenHands does that, I wrote about it if you search my submissions.
- andybak 1y agoI use it (and Codex web) specifically when I'm not at my desk (or I am but in the middle of something else) and I want to do something fairly speculative. Kinda either exploratory or investigative. I may or may not use the results but it doesn't get in the way of anything I'm actually currently doing. I mostly use Codex for this as I want to save my Claude quota for the task at hand.