feat(core): add server.enabled config option to restore HTTP server #8562
+5
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
server.enabledconfig option that explicitly enables the HTTP server for the TUI, restoring the pre-982b71e behavior for users who need external connections (desktop app, SDK, etc).Fixes #8561
Usage
{ "server": { "enabled": true } }Changes
config.ts: Addenabled: z.boolean().optional()to Server schemanetwork.ts: ReturnenabledfromresolveNetworkOptions()thread.ts: AddnetworkOpts.enabled ||toshouldStartServerconditionWhy
Since 982b71e ("disable server unless explicitly opted in"), users who need the HTTP server have no clean way to enable it:
port: 0fails (schema rejects non-positive)hostname: "127.0.0.1"doesn't trigger server (matches default)mdns: trueworks but has unwanted side effectsThis provides a clear, self-documenting opt-in with no side effects.
Testing
Tested locally - setting
"server": { "enabled": true }inopencode.jsoncorrectly starts the HTTP server.