> In my iteration on this, I’ve found that a pure agent loop is not the optimal shape for agentic monitors. Rather, a harness that allows the agent to write a spec of how to monitor, along with a deterministic system for running those specs, produces significantly cleaner signals with dramatically lower token usage.
Would be curious:
1. How / at what interval does it run those specs?
2. Are these basically just queries? Or what's included in a "spec" that an agent executes on?
Would be curious:
1. How / at what interval does it run those specs?
2. Are these basically just queries? Or what's included in a "spec" that an agent executes on?