@PovilasKorop Doing the review in @getpolyscope these days. Best experience as I can give the agent feedback to specific code lines as a comment. https://t.co/dUHVR4HDM5 goes the same direction.
@PovilasKorop Spot on. We literally made our decision that way. Had 2 sales calls with the cloud sales team and decided against having our own infrastructure via Hetzner/DO. We switched from vapor/AWS to Cloud and the costs has minimized by 50% in our case.
@taylorotwell - Failed jobs no longer live in my own database.
- No bulk delete in the UI for failed jobs
- Can’t send a colleague a direct link to a specific failed job
- Search doesn’t find anything in a failed job’s “payload” key
- The API doesn’t return the “payload” key for a failed job.
@PovilasKorop For me Solo and Polyscope are both amazing! Solo needs a diff view where I can write instructions for the agent on a specific line change but I think it’s coming soon from what I’ve heard in their podcast.
@IanLandsman By default disabled. Use the native agent team feature within Claude code. Tell Claude to spin up a team of 5 and Claude will decide automatically how many agents can work in parallel and where in your code base at the same time. https://t.co/bEkJu2srDU