Issue Summary
When running CodeNomad in server mode with the default HTTPS configuration, the browser shows a "Your connection is not private" warning due to the self-signed certificate. This is expected behavior, but is not mentioned anywhere in the getting-started documentation.
First-time users may not realize they can safely proceed through the warning for localhost, or that --https=false --http=true is available as an alternative.
Suggestions
- Add a note to the quick-start section that the self-signed cert will trigger a browser warning on first launch, and how to proceed (e.g., "Advanced" → "Proceed to localhost").
- Mention the HTTP-only alternative for local-only use:
npx @neuralnomads/codenomad --password <pw> --https=false --http=true
The server README's "Self-Signed Certificates" section documents the cert generation and SANs, but doesn't mention the browser warning that results from it.
Environment
- OS: Ubuntu 24.04 (Linux)
- Browser: Brave / Vivaldi
- Ran via:
npx @neuralnomads/codenomad --password <pw>
Co-Authored-By: Oz oz-agent@warp.dev
Issue Summary
When running CodeNomad in server mode with the default HTTPS configuration, the browser shows a "Your connection is not private" warning due to the self-signed certificate. This is expected behavior, but is not mentioned anywhere in the getting-started documentation.
First-time users may not realize they can safely proceed through the warning for localhost, or that
--https=false --http=trueis available as an alternative.Suggestions
The server README's "Self-Signed Certificates" section documents the cert generation and SANs, but doesn't mention the browser warning that results from it.
Environment
npx @neuralnomads/codenomad --password <pw>Co-Authored-By: Oz oz-agent@warp.dev