Skip to main content
Coming soon. Not in this release. This page says what the plugin is, so that the shape is public before the code is.
Put an agent built with eve into a seat, and the team around it stays the same. An eve agent becomes one Obversa engine: one node the runtime can review, run again with findings, resume and record, with the agent’s internals, its sessions, tools, skills and memory, left eve’s. A binding will name the eve agent the way claude('claude-sonnet-4-5') names a Claude seat, and a workflow() role will take it like any other engine. What the two frameworks each do, and where they overlap, is on Obversa and eve.

​
Next steps