Skip to main content

Module reload

Module reload 

Source
Expand description

Hot reload of the configuration: SIGHUP or lifecycle.watch_config re-merges the files and re-validates. The reload is all-or-nothing — if any restart-only path changed the whole reload is refused as restart_required and the running configuration stays, so the daemon never ends up half on one configuration and half on another.

The reloadable partition applies at the loop’s quiesce boundary. The flat child tree makes most of it trivial: every turn worker is spawned fresh from the live settings, so a new intelligence endpoint, model, instruction, budget, tool override or workflow definition takes effect for the next unit of work without touching the units already in flight. Live workflow runs keep the definition they started with, pinned by hash, so a run cannot change shape halfway through.