eforge-daemon-restart

To rebuild and restart a daemon after code changes, run a full build from the project root to compile the source, then stop, start, and verify the daemon is running with the updated code.

The best way to apply recent code changes to a running daemon is executing an end-to-end restart workflow that rebuilds from source, stops the old process, starts the fresh daemon, and verifies the new state is active.

You need to rebuild a daemon from source during development when you have modified code and require a fresh MCP-enabled daemon state to test or apply those recent changes in your development workflow.

Yes, the daemon restart workflow includes a verification step to confirm the daemon is actively running with the newly built code after the stop and start cycle completes.

Yes, you need to run from the project root directory to ensure the full build process correctly compiles the source code before stopping and restarting the daemon.

A manual restart might not reflect recent code modifications if the source was not fully rebuilt beforehand; an end-to-end build, stop, start, and verify workflow ensures the new code is loaded.