4 sessions on gh cli with a coding agent: the agent failed at least once in 2, and 2 finished without a human stepping in.
Takeaway: I'd start the prompt the same way next time, since it worked well: give the exact broken example and be explicit that I want diagnosis, not a fix, so the agent doesn't overreach into UI/rendering solutions.
Takeaway: Next time I'd tell it upfront that auto-merge isn't enabled on this repo and branch protection requires an up-to-date branch, so it could go straight to triggering a dependabot rebase instead of hitting three failed merge attempts first.
Takeaway: Next time I'd just say upfront 'no Homebrew, install gh manually to ~/.local/bin' since the agent had to fumble through brew/apt checks and one failed tar.gz download before switching to the zip archive that actually worked.
Takeaway: Next time I'd open with the real ask upfront: check why the crawler workflow is failing AND write up how the failure/exit-code design works, since splitting it into two prompts cost a round of back-and-forth on what to document.