Describe the request
Slack List operations so Cursor can:
Add rows: slackLists.items.create
Update rows/cells: slackLists.items.update
List rows: slackLists.items.list
and that the app will need lists:read and lists:write scopes.
Hi Thomas!
Thanks for the detailed request – and for including the specific API methods and scopes. That level of detail makes it much easier to evaluate on the engineering side.
I’ve shared this with our team as a feature request for extending the Slack integration’s capabilities. No timeline to share at this point, but we appreciate the feedback.
Feature request for product/service
Background Agent (GitHub, Slack, Linear,…)
Describe the request
TLDR; add lists:read to scope/permissions for the Cursor Slack Bot.
We are using Slack Lists/Items/Workflows for our bug reporting process. The workflow is the intake, and it then posts to #bug-reports a link to the Slack Item that was created (Items are hosted inside a List).
We are trialing using the Cursor bot to investigate bug reports (suggest team ownership, suggest troubleshooting, duplicate identification, etc), but because of the lack of this permission, the bot cannot read the full report (it can only see preview that is posted to the bug-reports slack channel).
It would be beneficial if the Cursor bot could also review these Lists/Items, much as it can read a channel. I’ve reviewed the config of the Cursor slack app and it does not appear to list this permission already. Just thinking that as the Slack infrastructure grows, so should the capability of the Cursor Automations bot within Slack.
Operating System (if it applies)
MacOS
Feature Request:
Cursor Slack Bot currently cannot fully read our reports because they are stored in Slack Lists/Items, and the bot lacks the lists:read permission. Right now it only sees the preview message posted, which limits its ability to investigate, identify duplicates, suggest troubleshooting, and recommend ownership. Adding lists:read would allow the bot to access the full report content and better support our Slack-based bug reporting workflow.
Feature Request: Cursor Bot Access to Slack Lists & Items
We currently use Slack Lists, Items, and Workflows to manage our bug reporting process. The workflow serves as the intake mechanism and posts a link to the created Slack Item in the #bug-reports channel (with each Item stored within a List).
We’re piloting the use of the Cursor bot to help analyze incoming bug reports—such as suggesting team ownership, identifying duplicates, and providing troubleshooting guidance. However, the bot is currently limited by permissions and can only access the preview shared in the channel, not the full contents of the Slack Item.
It would be highly valuable if the Cursor bot could also access and review Slack Lists and Items directly, similar to how it can read channel messages. Based on the current Slack app configuration, this permission does not appear to be available.
As Slack continues to expand its platform (e.g., Lists and structured Items), it would be beneficial for Cursor Automations to evolve alongside it and support these newer data structures.