# @cursor/sdk 1.0.35 + Grok 4.6 high: isolated no-tool runs drop or die with \[internal\] unable to open database file (2026-10-02)

**URL:** <https://forum.cursor.com/t/cursor-sdk-1-0-35-grok-4-6-high-isolated-no-tool-runs-drop-or-die-with-internal-unable-to-open-database-file-2026-10-02/173594>\
**Category:** Bug Reports\
**Tags:** cursor-sdk\
**Created:** [October 2, 2026, 12:04pm UTC](https://forum.cursor.com/t/cursor-sdk-1-0-35-grok-4-6-high-isolated-no-tool-runs-drop-or-die-with-internal-unable-to-open-database-file-2026-10-02/173594 "2026-10-02T12:04:30Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 20, 2026, 9:37am UTC](https://forum.cursor.com/t/cursor-sdk-1-0-35-grok-4-6-high-isolated-no-tool-runs-drop-or-die-with-internal-unable-to-open-database-file-2026-10-02/173594/22 "2026-10-20T09:37:02Z")

</div>

Hey @mad4thrash,

A change has landed so that when the SDK can’t open its local SQLite store, the run keeps going in memory (with a warning) instead of replaying the same turn and ending with `[internal] unable to open database file`. It will be included in an upcoming version of `@cursor/sdk`.

The Windows path-length cause is being handled separately. Until that’s in, `JsonlLocalAgentStore` with a short root folder is still the best option if you want run history kept on disk.

Let me know if you still hit the error after updating.

cc @Fabio_Paul_Bedoya_Hu

---

_[View the full topic](https://forum.cursor.com/t/cursor-sdk-1-0-35-grok-4-6-high-isolated-no-tool-runs-drop-or-die-with-internal-unable-to-open-database-file-2026-10-02/173594)._