Is Cursot Bot still available for use in my Cursor Profile

Support Help
,
1

image
image1008×254 14.9 KB

I’m trying to set up my new automation for triggering CI github actions to monitor failed or cancelled jobs and I got this error or warning message at the bottom of the screen.

I’m confused. I can’t find Cursor Bot anywhere.

Can someone please guide me?

5

Hey @Andy_Wong, thanks for the screenshot!

That warning is about the Send to Slack tool, not your GitHub CI trigger. “Cursor Bot” is the Cursor app in your Slack workspace, and it shows up in Slack as Cursor. It needs to be a member of a channel before the automation can post there.

To fix it:

  1. In Slack, open the #cursor-agents-catch-all channel.
  2. Type /invite @Cursor in the message box and send it.
  3. Back in the automation editor, open the channel dropdown next to “Send to Slack” and click “Refresh channels” (or reload the page).

The warning should then disappear. Your CI trigger works either way. The warning only affects whether the agent can post the results to that channel.

If it’s still there after inviting, let me know and we’ll take a closer look.

7

Thanks @Colin so much for that. That really help to diffuse the confusion I experienced with it for sometime.

The error went away.

Now I’m facing this when trying to test running the automation trigger.

image
image397×225 9.14 KB

Any idea what I should be doing with this?

11

Hey @Andy_Wong, glad the Slack part is sorted!

That message is expected for this trigger. “Run Test” can only simulate some trigger types, and “Workflow run completed” isn’t one of them yet. Your automation’s triggers are both of that type, so the test dialog can’t run it. The automation itself is saved and enabled, and it will run on real GitHub Actions events.

To test it for real:

  1. On a test branch in your repo, make a small commit that causes one of your GitHub Actions workflows to fail (for example, add a step that runs exit 1).
  2. Push that commit to GitHub.
  3. Wait for the workflow run to finish with “Failure” (or cancel it while it’s running to test “Cancelled”).
  4. Check your automation’s run history in Cursor, and your Slack channel, for the agent’s summary.

One important detail: right now this trigger only fires for workflow runs that were started by a push. Runs started with the “Run workflow” button, on a schedule, or by a pull request won’t start the automation, so please use a push when testing.

If you mainly care about CI on pull requests, the “Checks completed” trigger covers that case, and it does support “Run Test”.

Let me know how the push test goes!

12

Thanks @Colin for the detailed thorough walkthrough.

I will test it out when I’m ready to resume working on my specific repo to verify this behaviour.

I will come back to you with my observations thereafter!