feat(cli): warn when --port is outside discovery range

[IamCoder18]

Issue

Context

When kilo console --port <port> or kilo daemon start/restart --port <port> is called with an explicit port outside the daemon discovery range (4097–4116), the daemon still starts successfully but Kilo's browser auto-discovery only scans that 20-port window. This means later manual launches or dev-mode auto-connect can silently fail to find the daemon, leaving the user with no feedback about why the console can't connect.

The fix is to print a non-fatal yellow warning when an explicit port is passed outside that range, while still allowing the command to succeed normally.

Implementation

I added a small shared helper in a Kilo-owned path (packages/opencode/src/kilocode/cli/port-warning.ts) so the change avoids touching upstream shared files and doesn't require kilocode_change markers.

The helper warnIfPortOutsideDiscoveryRange(port):

• Skips the check when port === 0 (auto-pick mode).
• Reads the range from Daemon.PortRange (4097–4116).
• Emits a yellow console.warn when the explicit port is out of range.

I then called this helper from:

• packages/opencode/src/kilocode/cli/cmd/console.ts: after resolving network options and before Daemon.start().
• packages/opencode/src/kilocode/cli/cmd/daemon.ts: in both the start and restart handlers.

The warning is informational only; the command starts the daemon and opens the console as normal.

Screenshots / Video

How to Test

Manual/local verification:

• kilo daemon stop && kilo console --port 4097 → no warning.
• kilo daemon stop && kilo console --port 4321 → yellow warning, then console opens.
• kilo daemon stop && kilo console --port 0 → no warning (auto-pick).
• kilo daemon stop && kilo daemon start --port 5000 → yellow warning.
• kilo daemon stop && kilo daemon restart --port 5000 → yellow warning.

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

File	Line	Issue	Status
packages/opencode/src/kilocode/cli/port-warning.ts	N/A	warnIfPortOutsideDiscoveryRange renamed to warnPort — single-word name now matches style guide	✅ Fixed
N/A	N/A	No changeset — PR was missing a .changeset/*.md file for the user-visible warning	✅ Fixed

Files Reviewed (4 files)

• packages/opencode/src/kilocode/cli/port-warning.ts — clean
• packages/opencode/src/kilocode/cli/cmd/console.ts — clean
• packages/opencode/src/kilocode/cli/cmd/daemon.ts — clean
• .changeset/feat-cli-port-discovery-warning.md — correct package, bump level (patch), and user-facing description

---

_{Reviewed by claude-sonnet-4.6 · 137,820 tokens}

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