Hacker News Reader

px1999

My org has built internal tooling that approximates this. It's incredibly valuable from a manual test perspective though we haven't managed to get the agent part working well, app startup times (10+ min) make iterating hard.

Do you have customers who have faced/solved this problem? If so, how did they do it -- it seems like a killer on the approach?

View on HN

Our foundational design value was compute instance startup speed. We've made some design decisions and evaluated several "neocloud" providers with this goal in mind.

Currently, from launching an agent to that agent being able to run tests in our Rails docker-compose environment (and to the live app preview running), is about 30 seconds. If that agent finishes their work and goes to sleep, and then hours later you come back to send a message, it'll wake up in about the same time.

(And, of course, you can launch many agents at once -- they're all going to be ready at roughly the same time.)

Reply on news.ycombinator.com