Repository navigation
feat(studio): support private and shared Bot bindings - #1171
Merged
Merged
Conversation
warm-wm
approved these changes
Oct 16, 2026
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.
Studio currently omits
bindingType, so adding a Bot through the UI always relies on the Runtime default. This change adds an advertised Shared/Private choice to Feishu and Lark binding, with Shared as the default when available. QR creation, QR retry and manual binding forward the selection; retries keep the original type locked.The private description is intentionally concise: “私聊可召回同 Bot 的历史,包括群聊。” / “Private chats can recall this Bot’s history, including group chats.” Runtime authorization and recall isolation are unchanged.
botBindingTypesretains the legacy UI and request body. Other providers remain unchanged; Lark keepsdomain=lark.Validation:
No live Feishu registration/cloud deployment or real IME input was performed. Existing component IME and duplicate-submit regression passed. Full Python regression was not run because Python production code is unchanged. Existing toolchain warnings remain. This PR was based on
origin/mainatedae5b58.Design and verification:
prd-spec/features/bot-binding-types/2026-10-16-bot-binding-types.mdand its Chinese counterpart.CI follow-up (2026-10-16): all six upstream workflow runs are
action_requiredpending fork approval; no CI jobs have executed. The author account cannot approve them (GitHub returns 403, repository admin rights required). Re-ran the backend Sidecar gate locally: 289 tests passed and the coverage gate passed (96%). Frontend Sidecar gate: 22 tests passed, 100% lines / 94.44% branches. Full frontend suite and pre-commit passed again. These local results do not replace upstream CI approval or the Linux release-bundle smoke job. No code change was needed for the observed approval blocker.