Enable local HTTP API by default (MCP needs it)#258
Merged
Conversation
…ODE_LOCAL_API=0) The local API powers the MCP server and Claude Code's board automation. It was off unless KAITENCODE_LOCAL_API=1 was set, so a normal Dock/.deb launch wrote no ~/.kaitencode/api.port and every MCP mutation failed with "app is not running" — a silent, hard-to-diagnose footgun. Flip the default to ON. It's safe to default on: the server binds 127.0.0.1 only and authenticates every request with a per-run bearer token in a 0600 discovery file. Explicit opt-out is preserved: KAITENCODE_LOCAL_API=0 (or false/no/off) disables it. Updates the disabled-path log message and the README accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The local HTTP API powers the MCP server and Claude Code's board automation. It was off unless
KAITENCODE_LOCAL_API=1was set — so a normal Dock/.deblaunch wrote no~/.kaitencode/api.port, and every MCP mutation failed with "app is not running" (a silent, hard-to-diagnose footgun — hit it while setting up the dogfood board).Change: default the API to ON. Safe to do so — it binds
127.0.0.1only and authenticates every request with a per-run bearer token in a0600discovery file. Explicit opt-out is preserved:KAITENCODE_LOCAL_API=0(orfalse/no/off).Also updates the disabled-path log message and the README. New test covers the opt-out values; existing default test flipped to assert on. cargo test + clippy green.