Smart Node 1.12.52 was released on 17 October 2026. If you operate a Smart Node instance, several changes in this release affect how your daily digest is delivered, how updates run, how custom workflows survive updates, when the approval gate starts, and how the voice service confirms readiness after restart.
Your daily digest now arrives
The daily email digest that summarizes activity for your node used to work only on the first node you installed. On every other node, the system prepared the digest but could not deliver it because there was no mail path configured. The digest now uses the same delivery system that handles budget alerts and approval requests. The digest uses the email address you set in Settings and goes through on the same terms as budget alerts and approval requests: if something is misconfigured, the system tells you immediately instead of silently failing.
Updates complete in fewer steps
Before this release, the system repeated a configuration step after installing each service that makes up a Smart Node. The configuration check now runs once, after all companions are installed, instead of after each component. Additionally, updates now skip reinstalling components whose code and configuration have not changed. Your first update after this release runs in full. Later updates skip unchanged code.
Custom workflows no longer break updates
If a custom workflow creates its own folder during operation, the next platform update used to stop at the platform's setup check with no way to preserve what the workflow had stored. Operators can now declare custom folders in a settings file, using the same rules the platform applies to its own locations. A workflow that declares its folders correctly will survive a platform update.
The approval gate starts on fresh nodes
The Human-In-The-Loop approval gate enforces critical decisions: the owner must approve before agents send messages or publish content. On a fresh install, the gate used to fail because a required directory was not created early enough during startup. This is fixed. The gate now starts on first boot without issues.
Voice service confirms readiness on update
When a platform update restarts the voice service, the system checks that it is ready to accept requests. The check used to run too quickly and report failure even though the service was still starting. The check now waits for the service to be truly available before deciding the restart succeeded.