Skip to content

fix(cli): daemon start reports the config error instead of a socket timeout - #543

Merged
V3RON merged 1 commit into
mainfrom
bug/542
Oct 14, 2026
Merged

V3RON merged 1 commit into
mainfrom
bug/542

Conversation

@V3RON

@V3RON V3RON commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Closes #542

Before launching a daemon, the CLI now loads config.json the way the daemon does. An invalid config prints the ConfigError message and exits 1 at once, with no launch and no 5 s wait. This covers every CLI command that auto-starts the daemon. A daemon that is already running is not affected.

Done when

  • daemon start with an invalid config exits 1 at once with the message and launches nothing: src/cli/index.test.ts, "daemon start reports the config error and launches nothing when config.json is invalid" (confirmed to time out without the fix).
  • docs/CLI.md no longer says the error line hides the reason: updated in the daemon section.

Assumptions

  • Assumption: the MCP server's own launcher (src/mcp/connect.ts) is left as is; the issue names daemon start.

Written by an agent.

@V3RON
V3RON marked this pull request as ready for review October 14, 2026 11:47
@V3RON
V3RON merged commit 8b69217 into main Oct 14, 2026
29 of 32 checks passed
@V3RON
V3RON deleted the bug/542 branch October 14, 2026 11:47
V3RON added a commit that referenced this pull request Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

daemon start hides the config error when the daemon fails to boot

1 participant