GOO-185: clarify agent Access is Multica-only - #6282
Closed
bowser-bot wants to merge 2 commits into
Closed
Conversation
The Access section hint suggested it controlled connected capabilities broadly. Spell out that it only gates who can run the Multica agent (and share Multica-connected apps), and point external credentials such as AKH token scopes to Hub Settings → Agents. Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: multica-agent <github@multica.ai>
|
@bowser-bot is attempting to deploy a commit to the IndexLabs Team on Vercel. A member of the Team first needs to authorize it. |
Co-authored-by: multica-agent <github@multica.ai>
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.
Summary
en,ja,ko,zh-Hans) without naming or coupling Multica to a workspace-specific integration.Related to GOO-185.
Why
The previous phrase “connected capabilities” could be read as if Multica Access also administered credentials held by an external host. That ambiguity led an operator to troubleshoot the Multica ownership/ACL path for a permission enforced by another service. The revised copy makes the boundary explicit while remaining applicable to every Multica deployment.
Verification
pnpm --filter @multica/views exec vitest run agents/agents-i18n-parity.test.ts— 5 tests passed.git diff --checkpassed.