custom server port not respected #27

New issue

Closed

opened 2026-04-16 02:20:00 -07:00 by disberd · 3 comments

disberd commented

2026-04-16 02:20:00 -07:00

(Migrated from github.com)

Hi, Thanks a lot for this package which seems super neat!

I am trying to run Kaimon with a custom port instead of 2828.

I set a different port in the setup, and I correctly see the changed port in the ~/.config/kaimon/config.json

Unfortunately when starting the kaimon app, it looks like the setting is ignored based on the TUI:

Is this a bug?

Hi, Thanks a lot for this package which seems super neat! I am trying to run Kaimon with a custom port instead of 2828. I set a different port in the setup, and I correctly see the changed port in the ~/.config/kaimon/config.json Unfortunately when starting the kaimon app, it looks like the setting is ignored based on the TUI: <img width="774" height="297" alt="Image" src="https://github.com/user-attachments/assets/490fcd15-def9-4005-b75a-199ce6ac9f9c" /> Is this a bug?

kahliburke commented

2026-04-16 03:00:08 -07:00

(Migrated from github.com)

@disberd Looks like it is, there is a command line option which is used but it doesn't respect the config.json setting. I'll fix it and put out a patch release, but you can get around it now with:

Kaimon — persistent MCP server with terminal dashboard

Usage: kaimon [options]

Options:
  -p, --port PORT             MCP HTTP server port (default: 2828)

@disberd Looks like it is, there is a command line option which is used but it doesn't respect the config.json setting. I'll fix it and put out a patch release, but you can get around it now with: ``` Kaimon — persistent MCP server with terminal dashboard Usage: kaimon [options] Options: -p, --port PORT MCP HTTP server port (default: 2828) ```

❤️ 1

kahliburke commented

2026-04-16 03:03:08 -07:00

(Migrated from github.com)

@disberd - 1.3.1 on the way

kahliburke commented

2026-04-16 03:03:22 -07:00

(Migrated from github.com)

Fixed in v1.3.1. The TUI entry point (@main) was only checking --port from CLI args and falling back to the hardcoded default, never reading from config.json. The headless path already did the right thing — the TUI now matches.

Priority: CLI --port > config.json port field > default 2828.

Thanks for the report!

Fixed in v1.3.1. The TUI entry point (`@main`) was only checking `--port` from CLI args and falling back to the hardcoded default, never reading from `config.json`. The headless path already did the right thing — the TUI now matches. Priority: CLI `--port` > `config.json` `port` field > default 2828. Thanks for the report!