This page doesn't emphasize the cordis architecture [1], but that's the most exciting thing about this -- not just yet another harness. It has the potential to make this into something like the emacs of harnesses! I think this might be particularly potent for long-running agents.
It's no that fancy when is put in practical engineering terms. I've spend some time with the paper.
Paper describes such system whch has ability to enable/disable capabilities without process restart. Each plugin must follow specific shape: function to activate, function to deactivate it (both working, mutating the same shared context object), describe provided and required services. This, plus some ideas, like "every provider must outlive consumers when destructred" allows plug-n-play ensuring all dependencies are satisfied before the plugin is activated, lazy activation, and plugin deactivation/destruction.
ssivark · · focus · HN ↗
[1] <a href="https://arxiv.org/abs/2608.25512" rel="nofollow">https://arxiv.org/abs/2608.25512
podgorniy · · focus · HN ↗
Paper describes such system whch has ability to enable/disable capabilities without process restart. Each plugin must follow specific shape: function to activate, function to deactivate it (both working, mutating the same shared context object), describe provided and required services. This, plus some ideas, like "every provider must outlive consumers when destructred" allows plug-n-play ensuring all dependencies are satisfied before the plugin is activated, lazy activation, and plugin deactivation/destruction.
dgellow · · focus · HN ↗
ta20240528 · · focus · HN ↗
nicce · · focus · HN ↗