When something needs a hand
Find the first failing step and preserve the information needed to recover.
Documentation for Nookins 0.42.1-alpha.1 · Public alpha
The installer refuses the destination
Fresh installation needs an absent directory. Do not delete an existing home to make it pass. For a native Nookins home, use the updater. For Ward, retain the original and recreate selected agents separately.
An operation was interrupted
Keep the exact command output, operation records, old generation, and maintenance files. Follow the command's reported recovery instructions. Do not delete ownership state, rename paths, or switch homes as an improvised fix. Repeat consolidation only after resolving any reported blocking condition.
The service runs but there is no reply
Check that both terminals select the same home, then inspect:
"$NOOKINS_HOME/bin/nookins" --version
"$NOOKINS_HOME/bin/nookins" service status
"$NOOKINS_HOME/bin/nookins" agent codex statusTest the configured agent ID in the local console. A provider may need authentication even when the service is healthy. Keep messaging disabled until the local acceptance check passes.
Messaging replies twice or uses the wrong agent
Stop the trial. Check that Ward is stopped, verify the account and route, and apply configuration only with Nookins stopped. Start with one owner-only direct conversation. Do not solve duplicate replies by adding more routes.
Send a useful report
Use feedback and include:
- Nookins version and operating system.
- Whether this was a fresh install or an update.
- Which steps passed.
- The first failing command and its error, with sensitive values removed.
Leave out credentials, tokens, pairing codes, private messages, and complete home or database archives. For suspected vulnerabilities, follow private security reporting.