claude-code - 💡(How to fix) Fix [BUG] slack_read_channel / slack_read_thread drop message attachments and blocks [1 participants]

Error Messages/Logs

TL;DR

The issue can be addressed by modifying the slack_read_channel and slack_read_thread tools to parse and return content from attachments and Block Kit blocks in addition to the top-level text field.

Guidance

• Review the implementation of slack_read_channel and slack_read_thread to identify where the parsing of Slack message content is happening and modify it to include attachments and Block Kit blocks.
• Specifically, ensure that the tools are extracting and returning attachments[].fallback, attachments[].text, attachments[].fields[].title, attachments[].fields[].value, and plain-text and mrkdwn leaf nodes from the blocks[] tree.
• Test the modified tools with a variety of Slack messages that use attachments and blocks to verify that the content is being correctly surfaced.
• Consider adding logging or debugging statements to help identify any issues that may arise during the parsing process.

Example

No code example is provided as the issue does not include specific implementation details.

Notes

The solution will depend on the specific implementation of the slack_read_channel and slack_read_thread tools, which is not provided in the issue. Additionally, the issue does not specify the programming language or framework being used, which may impact the solution.

Recommendation

Apply a workaround by modifying the slack_read_channel and slack_read_thread tools to parse and return content from attachments and Block Kit blocks, as this will allow the tools to correctly surface content from Slack messages that use these features.