Feature request: Allow bots to follow threads they create

Scenario

In a group chat, a user mentions a bot in a normal group message. The bot replies in a thread, creating or joining a focused discussion for that request.

After that, the bot only needs to care about follow-up replies in that specific thread. It does not need to receive or inspect unrelated messages from the whole group chat.

Expected behavior: follow-up replies in that thread should not need to mention the bot every time. The bot should still be able to receive those thread replies and decide whether to respond.

Current limitation

Current app setup:

• Permission: im:message.group_at_msg:readonly
• Permission: im:message:send_as_bot
• Event subscription: im.message.receive_v1

With only im:message.group_at_msg:readonly, the bot can receive group messages that mention the bot, but it cannot receive non-mention replies in the thread created by the bot's reply.

With im:message.group_msg:readonly or im:message.group_msg, the bot receives all user messages in every group chat where it is present. This permission is too broad for apps that only need to follow the thread created by the bot's own reply.

In practice, app developers may not want the bot to receive a high volume of unrelated group messages just to support follow-up replies in one thread.

Requested capability

Please provide a more granular event or permission:

• After a bot replies in a thread, allow the bot to receive subsequent user replies in that thread.
• Limit the event scope to those bot-created or bot-joined threads only.
• Do not require the bot to read all messages in the entire group chat.

This would enable more natural bot interactions in group threads while avoiding overly broad group message permissions.

The issue names no repository files, tests, or entry points; begin by checking whether the CLI exposes the listed messaging permissions or event subscription. Confirm whether the requested thread-scoped behavior can be implemented in this repository or requires an upstream Lark API change; done means documented support for receiving replies in bot-created or bot-joined threads without broad group-message access.