Repository navigation
docs(ai): document enabling per-user Claude Code Connect (Features__Ai__Clis__ClaudeCode) (#324) - #335
Merged
Conversation
…i__Clis__ClaudeCode) (#324) Add an "Enabling per-user Claude Code Connect" section to ModelProviderSetup that documents, in one place, the enablement path and prerequisites for the per-user Claude Code Connect flow (each user connects their OWN Claude subscription via Settings -> Models -> Connect, billed personally): - What Connect is (own-subscription CLI/token, not a personal API key) and how it is resolved (ResolveConnectToken/ResolveConnectCredential read the per-user {user}/_Memex/ClaudeCode node, not by model id). - Independent of the shared org Anthropic key (Features__Ai__Providers__Anthropic); enabling Connect ADDS the per-user card, does not change the shared key. - Prerequisites/enablement: CLI-enabled portal-ai image (bundles the claude CLI), Features__Ai__Clis__ClaudeCode=true, ClaudeCode:ConfigDirRoot per-user mount, redeploy. - Verification steps + cross-references to ModelProviderSettings and the /provider-keys skill. Every claim grounded in code: MemexConfiguration.cs, MemexFeatureOptions.cs, ChatClientCredentialResolver.cs, ClaudeCodeHarness/Configuration, the Connect/ backend, and the deploy image/config. Fixes #324 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
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.
Summary
Documents, in one place, how to enable per-user Claude Code Connect — each user connects their own Claude subscription via Settings → Models → Connect (billed to their personal account), gated behind
Features__Ai__Clis__ClaudeCode. The backend already exists; this fills the doc gap so a deployment can turn it on without reverse-engineering the code.Extends
src/MeshWeaver.Documentation/Data/AI/ModelProviderSetup.mdwith a clearly-headed "Enabling per-user Claude Code Connect" section (plus a forward-link from the existing Claude blockquote and a Related entry).What it documents (every claim grounded in code)
claude setup-token,ClaudeConnectStrategy) captures the user's subscription token and stores it encrypted at{user}/_Memex/ClaudeCode(ConnectTokenSink→ModelProviderService.CreateProvider/RotateKey).ChatClientCredentialResolver.ResolveConnectToken/ResolveConnectCredential, consumed byClaudeCodeHarness.Features:Ai:Providers:AnthropicandFeatures:Ai:Clis:ClaudeCodeare separate flags inMemexConfiguration.cs; enabling Connect adds the per-user card.portal-aiimage (bundles theclaudeCLI,deploy/base-images/portal-ai/Dockerfile);Features__Ai__Clis__ClaudeCode=true;ClaudeCode:ConfigDirRootper-user writable mount (ClaudeCodeConfiguration.ConfigDirRoot→CLAUDE_CONFIG_DIR); redeploy.Note on "off by default"
The code default for the flag is
true(absentFeaturessection = all-on, no regression, perMemexFeatureOptions), but the packaged deployment paths ship it off (deploy/.env.example=false; the Marketplace "Bundle co-hosted CLIs" checkbox unchecked) and it is inert without the CLI-enabled image. The section documents this precisely rather than asserting a code-level default.Verification
DocumentationLinkIntegrityTest— Passed (1/1). New links use/Doc/…,/Skill/provider-keys, and same-page anchors.Fixes #324
🤖 Generated with Claude Code