fix: bind tokenless examples to loopback - #57
Merged
Conversation
cmcp-runtime now restricts tokenless dev mode to loopback addresses (a wildcard or LAN bind requires CMCP_BEARER_TOKEN). The financial-services, healthcare, and startup-tpm examples run tokenless in dev mode and bound 0.0.0.0:8443, so they would fail to start on the current runtime. Bind them to 127.0.0.1:8443 and note why. industrial-embodied-ai already binds loopback. Verified all three gateways start cleanly on loopback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
cmcp-runtimenow restricts tokenlessCMCP_DEV_MODE=1to loopback binds (a wildcard/LAN bind requiresCMCP_BEARER_TOKEN; see cmcp #408). Thefinancial-services,healthcare, andstartup-tpmexamples run tokenless and bound0.0.0.0:8443, so they now fail to start with a "tokenless development mode may only bind to a loopback address" error.Bind those three to
127.0.0.1:8443(with a short note on why) and fix the startup-log snippet in the startup-tpm README.industrial-embodied-aialready binds loopback and its agent uses a token, so it's untouched.Verified: all three gateways start cleanly on loopback with the current runtime.
🤖 Generated with Claude Code