fix(cli): restart daemon when console requested host/port don't match

[IamCoder18]

Issue

Fixes #11137

Context

kilo console with explicit --port or --hostname options silently reuses a running daemon on a different host/port, ignoring the user's request. Since the server binds once at startup, there is no way to change the bind address of a running process — a restart is required.

Implementation

Extracted daemon startup logic into an exported startDaemon helper that checks whether the returned state is a reuse and whether it differs from the requested options. When a mismatch is detected and restartOnMismatch is true, it logs a warning, calls Daemon.stop(), and restarts with Daemon.start(opts).

The restartOnMismatch flag is only enabled when explicit --port or --hostname CLI arguments are detected in process.argv, preventing unnecessary restarts when the user runs kilo console without flags (which defaults to port 0 for auto-assignment).

Also added tests to verify functionality in the future.

Key design decisions:

• Port mismatch ignores opts.port === 0 (auto-port) to avoid restarts on default invocations

Screenshots / Video

before	after

How to Test

Manual/local verification

• kilo console --port 4097 starts daemon on 4097, then kilo console --port 4321 shows a warning and restarts on 4321
• kilo console without flags reuses the existing daemon without restarting

Reviewer test steps

1. Run kilo daemon stop to ensure clean state
2. Run kilo console --port 4097 — confirm URL shows port 4097
3. Run kilo console --port 4321 — confirm a warning is printed, daemon restarts, and URL shows port 4321
4. Run kilo console — confirm it reuses the daemon on port 4321 without restarting

Checklist

• Issue linked above, or exception explained
• Tests/verification described
• Screenshots/video included for visual changes, or marked N/A
• Changeset considered for user-facing changes
• I personally reviewed the diff and can explain the changes, including any AI-assisted work.

Get in Touch

Discord: @IamCoder18

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Resolved Issues (from previous reviews)

• Manual stop+start bypasses Daemon.restart() — Resolved. console.ts and daemon.ts now call Daemon.ensure(), which uses the internal run() helper with the flock — no separate stop+start.
• TOCTOU race — freePort()/port() releases the probed port before daemon binds it — Resolved. The freePort()/port() helpers are gone entirely. The test file is now pure unit tests with no live port probing.
• afterEach guard concern — Resolved. The afterEach and env-restore teardown are gone; the new tests are synchronous unit tests with no process state.
• All other previously raised issues remain resolved.

What changed in this update

• daemon.ts: Added Network Zod schema (with cors dedup+sort normalization), persists options in daemon state, extracts internal run() helper, adds matches() and ensure() exports, fixes restart() to run inside the lock, adds KILO_TEST_DAEMON_EPHEMERAL_PORT escape hatch in port() so tests use OS-assigned ports.
• console.test.ts: Completely replaced live integration tests with synchronous unit tests for Daemon.matches() and explicitNetworkOptions(). No live daemon processes, no TOCTOU risk.
• daemon.test.ts: Adds KILO_TEST_DAEMON_EPHEMERAL_PORT: "1" to test env so the live daemon test uses an OS-assigned port; loosens port assertion from range check to > 0.

Files Reviewed (5 files)

• packages/opencode/src/kilocode/cli/cmd/console.ts — uses Daemon.ensure() correctly
• packages/opencode/src/kilocode/cli/cmd/daemon.ts — uses Daemon.ensure() correctly, correct 3-way message
• packages/opencode/src/kilocode/daemon/daemon.ts — matches(), ensure(), run() logic all correct; cors normalization and vacuous-truth for empty explicit list handled properly
• packages/opencode/test/kilocode/cli/cmd/console.test.ts — unit tests cover all match/mismatch/legacy-state cases
• packages/opencode/test/kilocode/daemon.test.ts — ephemeral port env var correctly propagated; loosened assertion is appropriate

---

_{Reviewed by claude-4.6-sonnet-20260217 · 1,048,861 tokens}

_{Review guidance: REVIEW.md from base branch main}

[kilo-code-bot]

WARNING: TOCTOU race — port() closes the server before the daemon binds it

The helper probes an OS-assigned free port by listening on port 0, then immediately closes the server and returns the port number. Between server.close() completing and the daemon calling bind(), another process (or another concurrent test) can grab that port. On a loaded CI host this is a low-probability but real flake source.

The port: 0 auto-assign path used elsewhere (e.g. lines 92, 111) avoids this entirely — the OS holds the binding until listen() succeeds. If the test genuinely needs to verify that the daemon binds a specific user-supplied port, consider passing port: 0 and then asserting result.state.port !== 0, or accept the small risk given the narrow test-only scope.

---

_{Reply with @kilocode-bot fix it to have Kilo Code address this issue.}