The Node crash originates inside sqlite in the cursor-agent runtime

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

{“imageOffset”:1101988,“symbol”:“node::OnFatalError(char const*, char const*)”,“symbolLocation”:248,“imageIndex”:0},{“imageOffset”:833276,“symbol”:“napi_fatal_error”,“symbolLocation”:164,“imageIndex”:0},{“imageOffset”:22516,“symbol”:“Napi::Error::Fatal(char const*, char const*)”,“symbolLocation”:24,“imageIndex”:2},{“imageOffset”:12612,“symbol”:“Napi::Error::ThrowAsJavaScriptException() const”,“symbolLocation”:220,“imageIndex”:2},{“imageOffset”:26000,“symbol”:“Napi::Function::Call(napi_value__, unsigned long, napi_value__ const*) const”,“symbolLocation”:68,“imageIndex”:2},{“imageOffset”:86600,“symbol”:“node_sqlite3::Statement::Work_AfterPrepare(napi_env__, napi_status, void)”,“symbolLocation”:440,“imageIndex”:2},

Steps to Reproduce

Unable to open directly

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2025.11.25-d5b3271

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. This looks like a serious low-level crash in the cursor-agent SQLite database.

To help with diagnostics, could you share:

  1. The full crash log/stack trace (if there’s more detail)
  2. The exact command you ran (e.g., cursor-agent, cursor-agent "prompt", or something else)
  3. Your macOS version (System Settings > General > About)
  4. Did this happen on the first CLI run or after several successful runs?
  5. The full terminal output right before the crash

I’ll escalate this bug to engineering for further investigation.

3

cursor-agent,
mac version:15.3.1 (24D70)
How can I get more information? There are absolutely no error messages. It was working normally in the morning, but suddenly it wouldn’t start in the afternoon.

4

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.