Update Nookins

Before the update

Select the actual existing Nookins home. Keep your normal backup and note your agent names. Stop the foreground process with Ctrl-C, or stop the installed service using its normal service procedure. Keep the existing updater settings and recovery files in place until the update succeeds.

Whole-install Ward migration is retired. This procedure is for native Nookins homes. For Ward, recreate selected agents separately.

Check and update

export NOOKINS_HOME="$HOME/.nookins" # Your existing Nookins home.
"$NOOKINS_HOME/bin/nookins" --version
"$NOOKINS_HOME/bin/nookins" update --check
"$NOOKINS_HOME/bin/nookins" update
"$NOOKINS_HOME/bin/nookins" --version

The check inspects the selected signed release feed; it does not install an update. Confirm the installed version before proceeding.

Consolidate maintenance files

For the 0.41.1-alpha.1 layout and later, use the newly installed binary while Nookins is still stopped:

"$NOOKINS_HOME/bin/nookins" --home "$NOOKINS_HOME" maintenance consolidate
"$NOOKINS_HOME/bin/nookins" update --check
"$NOOKINS_HOME/bin/nookins" update

The public installer consolidates automatically. Existing 0.40/0.41 homes use their retained updater settings for the update, then consolidation moves maintenance records into $NOOKINS_HOME/maintenance. A repeated consolidation resumes or reports no work. Older full-bundle cache may remain.

If interrupted, preserve all remaining paths and repeat the same command. Busy or unfinished operations, custom paths, and collisions require resolving the reported problem first. Do not manually move or delete sibling files after a refusal. Retain the old generation and maintenance records for recovery.

Verify your Nookins

The final check and update should report up to date. Confirm your configuration and selected agents remain, then start Nookins normally. Workspace tools may take longer to prepare on the first start if enabled.

Repeat the local reply check and your one-conversation check. Provider login, real replies, and messaging are hands-on checks, not established by updater success alone.