How this helps you
Slack context and coding agents meet in one Bot chat instead of a copy-paste loop.
Look in [Slack channel or thread] for context about [bug or feature]. Summarise what matters, then message my live Cursor project [project name] with a clear task and the evidence. Report what the project replies. Do not merge, spend or deploy without my yes.
Fill in: [Slack channel or thread], [bug or feature], [project name]
What they did
In Q&A #1 Matt described Cursor Projects as one chat that spins sub-agents for several streams of work in a repo. With the Cursor plugin installed, Grok Bot can talk to any live Cursor agent. His example: a project is running, he asks Grok Bot to look in Slack for context, then message that project with what it found. He also noted an under-advertised feature: projects can message the Bots back, though you currently need to start the loop from the Bot. That turns Grok Bot into the meeting place between Slack context and coding agents without copy-paste.
Who it's for: Builders who already use Cursor Projects and keep context in Slack or email.
Before you start
- Cursor plugin connected in Grok Bot
- A Cursor Project (or live cloud agent) already running
- Slack or another context source connected if you want that handoff
How to try it
- Install and connect the Cursor plugin on the Bot that should manage coding work.
- Start or open the Cursor Project for the repo you care about.
- In Grok Bot, ask it to gather the missing context (for example from Slack) and message the live project with a clear ask.
- Watch for the project messaging back into the Bot chat; continue approvals there.
- Keep merge, spend and production deploys on explicit approval in the Bot you are watching.
What to expect
Grok Bot pulls a Slack thread, messages the Cursor project, and the project answers in the same Bot chat so you stay in one place.
Common mistakes
- Expecting the project to start the conversation first; Matt said you start from the Bot today.
- Letting the Bot merge without approval.
- Skipping the Cursor plugin connection and wondering why messaging fails.
Related tips
- Drive coding agents from your phone, then verify on a preview link: Ben Davis uses Grok Bot as the always-on manager for Cursor cloud agents and T3 Code, sends change requests from his phone, and only merges after he clicks through a preview.
- Make your Bot the manager, not the coder: one rule and locked doors: Let your Bot plan and check the work while coding agents write the code. Start with one rule, and remember every Bot shares one computer and its logins.
- A routine that triages your backlog with RICE and blast radius: Your Bot collects requests into a backlog, then a routine scores each item for reach, impact, confidence, effort and blast radius so the best small jobs rise to the top.
- From support form to fix: a webhook, a Bot and a Cursor cloud agent: A support form posts to a webhook, a Bot picks up the ticket, and for bugs it starts a Cursor cloud agent that reproduces the issue, adds a failing test and opens a pull request for an engineer to review.
Worth knowingFrom Matt Palmer, Grok Bot Q&A #1 (6 Nov 2026), around 15:19. Plugin and Projects UI can change; verify messaging still works on your build.Next in Workflows →Chain a whole errand into one prompt
Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot workflows tips