Do you have any examples of this approach?
Actors can have identities and roles for RBAC, etc. you - cross agent communication is the same as sending any other message to a actors.
Not to mention that actors can be on your device, another device, etc. whatever the router can resolve - it's transparent to the agents.
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.
Your technical ideas are just implementation details behind the interface. What's your idea for a better UX?
If you move away from the idea that agents are chat streams and treat them as processes/actors then you can start letting agents represent themselves/build their own interfaces.
And if you build enough introspection into the protocol because everything is message based you can have other agents build interfaces for them.
So like either standard GUI, or a voice assistant talking to you and delegating to agents, etc.
It's not an idea it's a way of thinking about agent systems - basically an agent OS.