fix(im): use tenant token for message history list#453
Open
xfcycc wants to merge 1 commit into
Open
Conversation
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
Fix Feishu IM message history reads by using tenant access token for
im.v1.message.list.get_as_userscopes fromfeishu_im_user_get_messagesfeishu_im_user_search_messageson user tokenCloses #356
Why
im.v1.message.listonly supports tenant access token. Calling it with user access token can fail with:The app type is not supportedAfter switching to tenant token, the API still requires the bot to be in the target chat. This PR keeps that limitation explicit in tool descriptions.
Test plan
pnpm buildpnpm lint— no errors, 21 pre-existing warningsfeishu_im_user_get_messagescan read group history with tenant token in local patched runtimefeishu_im_user_search_messagesremains user-token based