Cursor Automations webhook returns 401 ERROR_NOT_LOGGED_IN

Subject: Cursor Automations webhook returns 401 ERROR_NOT_LOGGED_IN (curl and Jira)

Description:

Hello,

I’m having trouble with Cursor Automations using a Webhook trigger. Outbound POST requests to the webhook URL fail with HTTP 401 and the following JSON body:

{

“code”: “unauthenticated”,

“message”: “[unauthenticated] Error”,

“details”: [

{

  "type": "aiserver.v1.ErrorDetails",

  "debug": {

    "error": "ERROR_NOT_LOGGED_IN",

    "details": {

      "title": "Authentication error",

      "detail": "If you are logged in, try logging out and back in.",

      "isRetryable": false

    },

    "isExpected": true

  }

}

]

}

What works

•Running the automation from the Cursor UI with JSON input completes successfully (release note / PR path behaves as expected).

What fails

•Calling the same webhook URL from Jira Automation (“Send web request”) → 401 with the error above (confirmed in Jira audit log).

•Calling the same webhook URL from curl on my machine with headers:

•Content-Type: application/json

•Authorization: Bearer <webhook API key copied from this automation’s Webhook settings> also returns 401 with the same error.

So the failure reproduces without Jira, using only curl + the documented Bearer token.

What I’ve already tried

•Confirmed header value is exactly Bearer crsr\_<token> (single Bearer, no Authorization: prefix in the value, no duplicate Bearer).

•Regenerated the webhook credential and updated Jira; duplicated the automation to get a new URL and token; issue persists.

•Verified URL and token are taken from the same automation in one session.

Request

Please help determine why the webhook endpoint rejects valid-looking Bearer authentication (ERROR_NOT_LOGGED_IN), or advise if there is a known issue, required header, account/plan requirement, or regional constraint for automation webhooks.

Details for your logs

•Cursor account email: [email protected]

•Automation page (ID only, no secrets): https://cursor.com/automations/f6e396e2-9436-4e55-b323-b91f6b77ba59

•Approximate test times (UTC): \[e.g. 2026-04-06 09:57 UTC, 2026-04-06 14:00 UTC\]

•Sample request: POST to webhook URL, JSON body \~{"issue_key":"TEST-1","issue_summary":"test","epic_key":"TEST-EPIC"}

I am not including the webhook URL or API key in this message for security; I can provide a redacted URL host/path or automation ID if you need a specific lookup.

Thank you.
Arjun

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Also getting cursor automation auth issues today

looks like it works now

Hi Arjun,

This is a confirmed server-side issue that’s been affecting webhook triggers since around April 4th. The error is not related to your API key, token format, or account – it was on our end.

The underlying cause has been identified, and a fix has been applied. Another user in this thread has already confirmed that webhooks are working again. Could you retry your webhook call and let me know if it’s working for you now?

If it’s still failing, please share the approximate time (UTC) of the failed attempt and I can check the backend logs.

Thanks for clarifying, Mohit. I checked this morning and things seem to be back in order. So do we have a permanent fix in place this time around? Just checking because I’ve observed that this is the second time this issue has cropped up.

Thanks for your help!
Arjun