Turn authenticated MCP tools into customer-branded CLI commands - #38
Merged
Merged
Conversation
elsheppo
force-pushed
the
codex/client-branded-capability-cli
branch
from
September 10, 2026 11:56
131f38c to
2ed7c2e
Compare
elsheppo
changed the title
elsheppo
marked this pull request as draft
September 18, 2026 17:51
elsheppo
changed the title
Merge the current Core line into the customer-CLI branch while preserving the reusable MCP-to-CLI runtime alongside the new Node and Next.js host targets. Generated CLIs continue to discover the signed-in user’s tools, store OAuth credentials in the operating-system keychain, require confirmation for writes, and call the original MCP endpoint directly. This does not publish a customer package. Verified with the full pnpm check: 214 tests passed, 3 skipped; build, packed-package, branded-CLI, and generated-project smoke checks passed.
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
1 participant
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.
Why
Chumbo Cloud needs a reusable way to turn an authenticated MCP tool surface into a customer-branded CLI without proxying application calls through Cloud. This PR adds that runtime to Chumbo Core.
What changes
Safety boundary
Credentials remain in the operating-system credential store and are partitioned by authorization issuer. Unknown tools default to write risk. Non-interactive writes fail unless explicitly confirmed. Chumbo Cloud does not enter the application data path.
Verification
Not included
This PR does not publish a customer package or implement the Chumbo Cloud configuration, preview, repository delivery, or release workflow. Those product capabilities will consume this reusable Core runtime.