---
title: "Comment by Kartik N V J K on \"Here Be Monsters: What Do You Still Need to Know When Agents Do the Work?\" | Hashnode"
description: "Level-triggered fits agent lifecycles well. If the loop compares what should be running with what is running on every pass, a crashed subagent can't slip throug"
url: "https://hashnode.com/posts/here-be-monsters-what-do-you-still-need-to-know-when-agents-do-the-work/6ae03c11e1c6135b06ad49ec/comment/6ae1fe8b3cbb4b197b976135"
---

[Discussion](https://hashnode.com/posts/here-be-monsters-what-do-you-still-need-to-know-when-agents-do-the-work/6ae03c11e1c6135b06ad49ec)

Comment [Here Be Monsters: What Do You Still Need to Know When Agents Do the Work?](https://hashnode.com/posts/here-be-monsters-what-do-you-still-need-to-know-when-agents-do-the-work/6ae03c11e1c6135b06ad49ec)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Oct 28](https://hashnode.com/posts/here-be-monsters-what-do-you-still-need-to-know-when-agents-do-the-work/6ae03c11e1c6135b06ad49ec/comment/6ae1fe8b3cbb4b197b976135)

Level-triggered fits agent lifecycles well. If the loop compares what should be running with what is running on every pass, a crashed subagent can't slip through because its exit event got lost, and that's the bug class I keep fighting in my own agent loops. When you rebuilt it, did the desired state live in a file the agents could read, or only inside the orchestrator?
