Post

I'm excited to announce a new open source project from @stacklok.com. Mecatl is a "cloud-native harness". The modern agent harness was born and built on the desktop. Current cloud hosting is largely "lift and shift". What if you built the harness *for* the cloud? joe.dev/posts/introd...

The engine/UI split raises a useful failure test: disconnect the client just as a tool requests approval, then reconnect from another device. Does the pending request live in durable session state? That seems as important as replaying the conversation for the mobile clients you describe.

The tool calls all happen engine-side. But they can be distributed too so there are network failure modes to consider. I’m working on attaching to sessions during approval calls now. Having the client be able to re-sync there is the goal.

Keeping a session running through an upgrade is a compelling use case. I'd test an approval that reaches the old leader but loses its acknowledgement, then gets retried from the phone against the new leader. The retry should resolve the same approval without scheduling the tool twice.