Description
Summary:
When a user enters an incorrect API key during onboarding, the key is immediately saved to ~/.nemoclaw/credentials.json. On subsequent nemoclaw onboard runs, the onboard wizard detects the stored key and skips the key input prompt, reusing the invalid stored value. Validation fails again with the same error, and the user has no way to re-enter the key through the CLI.
Steps to reproduce:
nemoclaw onboard → choose a provider → enter a wrong API key- Key saved to
~/.nemoclaw/credentials.json - Validation fails → exit or
back nemoclaw onboard again → wizard sees stored key → skips prompt → validation fails again
Expected behavior:
- When stored credential fails validation, the wizard should re-prompt for the key instead of silently reusing the invalid value.
- Or: provide a CLI command like
nemoclaw credentials reset to clear a stored credential.
Workaround:
Manually edit ~/.nemoclaw/credentials.json and fix or remove the invalid key.
Environment
- NemoClaw v0.0.7
- OpenShell 0.0.23
- OpenClaw 2026.3.11
- Node.js 22.22.1
Bug Details
| Field |
Value |
| Priority |
Unprioritized |
| Action |
Dev - Open - To fix |
| Disposition |
Open issue |
| Module |
Machine Learning - NemoClaw |
| Keyword |
GitHub, NemoClaw, NEMOCLAW_GH_SYNC_APPROVAL |
[NVB# 6056320]
[NVB#6056320]
Description
Summary:
When a user enters an incorrect API key during onboarding, the key is immediately saved to
~/.nemoclaw/credentials.json. On subsequentnemoclaw onboardruns, the onboard wizard detects the stored key and skips the key input prompt, reusing the invalid stored value. Validation fails again with the same error, and the user has no way to re-enter the key through the CLI.Steps to reproduce:
nemoclaw onboard→ choose a provider → enter a wrong API key~/.nemoclaw/credentials.jsonbacknemoclaw onboardagain → wizard sees stored key → skips prompt → validation fails againExpected behavior:
nemoclaw credentials resetto clear a stored credential.Workaround:
Manually edit
~/.nemoclaw/credentials.jsonand fix or remove the invalid key.Environment
Bug Details
[NVB# 6056320]
[NVB#6056320]