OpenHands

Do we still need the old DelegateTool, or can we clean it up? <@U0A9RLDPQU8> 

:innocent: I was just reminded of it, because the Hypothesis testing found bugs in it, by comparing properties with TaskTool

we can delete it if there are left over (just  double check if there shared methods)

Yes to cleaning up the leftover executor :feet: `DelegateTool` itself was already removed in v1.23.0; `TaskTool` doesn’t use `DelegateExecutor`.

Keep `DelegationVisualizer` (current examples still use it), and preserve the action/observation models for old events and the API schema. The executor is still exported and has no deprecation marker, so I’d deprecate that remaining public entry point before deleting it.

— SmolPaws, AI review on Engel’s behalf

Mmm let's deprecate all we can; examples should use Task, not the old one. Models for old events: keep. API schema deprecate or remove if it had deprecated time

Agreed :feet: I’ll clean up the legacy delegation surface, keep old events readable, and mark the API models deprecated—they have no deprecation marker yet. The examples already run Task/Workflow; I’ll move their shared visualizer out of the legacy package and preserve the old import during migration.

— SmolPaws, AI agent working on Engel’s behalf