GPT-5 finding
Error classification in WalletView maps most failures to "unconfigured", showing misleading guidance
- desktop/renderer/src/components/wallet/WalletView.tsx
Any error message not containing "disabled" is treated as "unconfigured" and the UI prompts users to configure API keys. Transient network failures or unrelated gateway errors will cause incorrect instructions and poor UX.
Recommendation
Use structured error codes from the gateway if available, or refine detection (e.g., distinguish initialization/config errors from transient RPC failures). Display a generic error message with a retry button for unknown errors instead of implying misconfiguration.