Webhook trigger endpoint returns 401 (regression, April 2026)

[bamieh]

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Title: Webhook trigger endpoint returns 401 (regression, April 2026)

Category: Bug Reports

Tags: automations, cloud-agents

Body:

My GitHub Actions workflow that triggers a Cursor automation webhook started returning 401 as of April 4. It was working correctly two days prior with no changes on my end.

What I’ve tried:

Regenerated the API key (new crsr_ token)
Authorization: Bearer
Authorization: Basic <base64(token:)>
curl -u :
Tested from both GitHub Actions and local machine
All return the identical response:

{
“code”: “unauthenticated”,
“error”: “ERROR_NOT_LOGGED_IN”,
“detail”: “If you are logged in, try logging out and back in.”
}
Endpoint: POST https://api2.cursor.sh/automations/webhook/

This appears to be the same server-side regression reported in Webhook trigger endpoint returns 401, which was fixed and has now regressed again.

Steps to Reproduce

steps:
  - name: Send issue to Cursor webhook
    env:
      CURSOR_WEBHOOK_URL: https://api2.cursor.sh/automations/webhook/6076a0ff-5b26-405e-82ef-d6173cd96066
      CURSOR_AUTH_TOKEN: ${{ secrets.CURSOR_AUTOMATION_TOKEN }}
    run: |
      set -e
      curl -fsSL -X POST "$CURSOR_WEBHOOK_URL" \
        -H "Authorization: Bearer $CURSOR_AUTH_TOKEN" \
        -H "Content-Type: application/json" \
        -d '{
          "issue_number": ${{ github.event.issue.number }},
          "issue_title": ${{ toJSON(github.event.issue.title) }},
          "issue_url": "${{ github.event.issue.html_url }}",
          "repo": "${{ github.repository }}"
        }'

Expected Behavior

It was working on Thursday, nothing changed in my setup it just started giving 401

Operating System

MacOS

Version Information

Just cursor cloud agents

Does this stop you from using Cursor

Yes - Cursor is unusable