Reload daemon configuration without restarting (#3365)
* feat(daemon): reload configuration without restarting Keep config validation, reloadability classification, override handling, and atomic runtime application inside the daemon so local and remote clients share one authoritative workflow. * fix(daemon): preserve reload resource ownership Keep every materialized provider client under daemon-lifetime ownership and classify speech overrides from resolved providers. Restore the complete WebSocket config-store test contract exposed by CI.
This commit is contained in:
@@ -202,9 +202,13 @@ Detaching is an explicit lifecycle action, not a creation flag. The agent keeps
|
||||
paseo daemon start # Start the daemon
|
||||
paseo daemon start --web-ui # Start and serve the bundled web UI
|
||||
paseo daemon status # Check status
|
||||
paseo reload # Reload config.json (top-level alias)
|
||||
paseo daemon reload # Reload config.json
|
||||
paseo daemon stop # Stop the daemon
|
||||
```
|
||||
|
||||
Reload validates the whole file, applies runtime-safe changes, and reports `appliedPaths`, `restartRequiredPaths`, and `overrideControlledPaths`. Human output prints `paseo daemon restart` only when a changed setting needs it. Use `--json` or `--format yaml` for the structured result, and `--host` to reload a remote daemon's own configuration file. An older host that does not support reload returns an update-host error.
|
||||
|
||||
Use `PASEO_HOME` to run multiple isolated daemon instances.
|
||||
|
||||
## Hub
|
||||
|
||||
Reference in New Issue
Block a user