Comment by solarkraft

I’d think the approach in this repo gets close to that, no? I also think LLM harnesses should just support typical async i/o.

Let a model get notifications when something it has accessed/ subscribed to changes, a tool produces output or it gets some other kind of message (for example by another AI or flesh agent). Wait until the next turn or wake it up. It can still decide to do nothing and wait.