Port env var mismatch — server.js uses PORT but config documents LAUNCHER_PORT #47

New issue

Closed

opened 2026-05-14 15:36:15 +00:00 by Mark · 1 comment

Mark commented

2026-05-14 15:36:15 +00:00

Owner

Bug

server.js reads the port from process.env.PORT || 8000, but config.js documents LAUNCHER_PORT and the AGENTS.md references LAUNCHER_PORT. This mismatch means:

Users following the docs and setting LAUNCHER_PORT won't actually affect the port the server binds to
The env var convention is inconsistent within the same codebase

Fix

Align on a single env var name — either change server.js to read LAUNCHER_PORT (matching the docs), or update the docs to reference PORT.

## Bug `server.js` reads the port from `process.env.PORT || 8000`, but `config.js` documents `LAUNCHER_PORT` and the AGENTS.md references `LAUNCHER_PORT`. This mismatch means: 1. Users following the docs and setting `LAUNCHER_PORT` won't actually affect the port the server binds to 2. The env var convention is inconsistent within the same codebase ## Fix Align on a single env var name — either change `server.js` to read `LAUNCHER_PORT` (matching the docs), or update the docs to reference `PORT`.

Mark commented

2026-05-15 13:46:27 +00:00

Author

Owner

Approved as bug. PORT vs LAUNCHER_PORT — align on a single env var name.