Skip to content

fix: bind tokenless examples to loopback - #57

Merged
imran-siddique merged 1 commit into
mainfrom
fix/loopback-dev-mode
Jul 24, 2026
Merged

fix: bind tokenless examples to loopback#57
imran-siddique merged 1 commit into
mainfrom
fix/loopback-dev-mode

Conversation

@imran-siddique

Copy link
Copy Markdown
Contributor

cmcp-runtime now restricts tokenless CMCP_DEV_MODE=1 to loopback binds (a wildcard/LAN bind requires CMCP_BEARER_TOKEN; see cmcp #408). The financial-services, healthcare, and startup-tpm examples run tokenless and bound 0.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-ai already 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

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>
@imran-siddique
imran-siddique merged commit 738b268 into main Jul 24, 2026
16 checks passed
@imran-siddique
imran-siddique deleted the fix/loopback-dev-mode branch July 24, 2026 18:11
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.

1 participant