Default port is now 1984 everywhere

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YShymaPrXmc3KYRUg2HMSs
This commit is contained in:
ariandClaude Sonnet 5.5 committed 2026-10-16 11:18:47 -04:00
1 parent dbe8a8d4e0
commit bdccace271
9 files changed
+35 -35

No files matched your search

+2 -2
View File
@@ -108,11 +108,11 @@ The MCP spec requires Origin validation on Streamable HTTP servers. If the pinne
---
## DEC-9 — Port 1984 in the NixOS module, loopback by default
## DEC-9 — Port 1984 by default, loopback by default
**Status:** Decided 2026-10-16
The module defaults `port = 1984` and `bind = "127.0.0.1"`. The binary's own default is unchanged. Exposing the service to the LAN is an install-time choice made in the host's own config, never a default: the operator sets `bind`, `openFirewall` (or an interface-scoped rule) and `allowedHosts` for that deployment. Config validation already refuses auth-off on a non-loopback bind, and a non-loopback bind without TLS logs a warning (see DEC-12).
The binary and the NixOS module both default to `port = 1984` and `bind = "127.0.0.1"` (the binary default was 9109 until 2026-10-16, when the user made 1984 the default everywhere). Exposing the service to the LAN is an install-time choice made in the host's own config, never a default: the operator sets `bind`, `openFirewall` (or an interface-scoped rule) and `allowedHosts` for that deployment. Config validation already refuses auth-off on a non-loopback bind, and a non-loopback bind without TLS logs a warning (see DEC-12).
**Decision:** Accepted by the user. The default is loopback. Installs change the relevant settings.