Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's safer have them completely isolated, but it's slower and more expensive.

Sometimes I just realize that CC going nuts and stop it before it goes too far (and consume too much). With this async setup, you may come after a couple of hours and see utter madness(and millions of tokens burned).



Completely agree. I also want to tightly control the output, and the more it just burns and burns the more i become overwhelmed by a giant pile of work to review.

A tight feedback loop is best for me. The opposite of these async models. At least for now.


You need a supervisor agent to periodically check the progress and `if (madness) halt(1)`




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: