[BUG] Error: DB storage not supported
Resolved 💬 18 comments Opened Apr 25, 2025 by 8W9aG Closed Apr 26, 2025
💡 Likely answer: A maintainer (igorkofman, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [x ] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 0.2.84 (Claude Code)
- Operating System: macOS 15.3.2 (24D81)
- Terminal: Terminal App
Bug Description
After inputting any prompt to claude I see the following:
Error: DB storage not supported
at file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:501:24798
at D (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:474:12907)
at uT1 (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:501:25784)
at ou0 (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:501:25908)
at RA6 (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:1874:6178)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async x80.<anonymous> (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:1875:817)
at async x80.parseAsync (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:465:4184)
at async eI8 (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:1878:4348)
at async rI8 (file:///opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js:1874:43981)
Steps to Reproduce
This happens to me with the following command: claude -p {prompt}
Expected Behavior
No crash.
Actual Behavior
Crash.
Additional Context
Was initially working and then began failing constantly with this message.
18 Comments
@8W9aG is this correct bug? Your description does not mention
DB storage not supportedI do actually get this error. I haven't run into this before. On a side note, why does my claude say offline? (on bedrock)
● Task(Explore the repository to give a high-level overview of the project. …
Check the README.md files, main entry points like main.py, and key files
to understand what this project does.)
⎿ DB storage not supported
<img width="849" alt="Image" src="https://github.com/user-attachments/assets/cb2b2a88-691a-439a-97e4-7a10fc9d9d95" />
I've never gotten the stack trace listed under the bug description. But I get the message that @abazabaaa has posted. But not the offline message.
Apologies its just before the stack trace:
Awesome, ill drop my issue then.
I have the same 'DB storage not supported', started after today's latest update. Never seen it before. Ubuntu 24.04 WSL.
Just saw this error as well with -p on WSL
getting this with -p on Debian 12 as well, started today.
Quick fix is to downgrade: npm install @anthropic-ai/claude-code@0.2.81
Also getting this today consistently with
-pon Ubuntu 24.04workaround for me is to use the version from yesterday for now
Same issue on Mac OS as of now:
I use claude code almost all day, almost every day, so this seems recent as I'd never seen it before.
As FYI, still happening for me on OSX as of 0.2.85
Mac M1. Tasks seem to continue without issue, though not clear.
<img width="548" alt="Image" src="https://github.com/user-attachments/assets/5b0ddefe-b093-4675-9ae4-a03e53c7057f" />
<br/>...<br/>
<img width="548" alt="Image" src="https://github.com/user-attachments/assets/670947f3-bce9-45e3-9dbe-be1e03db3a04" />
<br/>...<br/>
<img width="548" alt="Image" src="https://github.com/user-attachments/assets/d0fa2626-43bc-43c0-9040-c454c0bbc072" />
Another Observation
Claude Code generally seems slower.
+1
just merge that PR where you have the DB and cut a release already 😂
+1
Oof. We're looking into it now.
We've published a fix in 0.2.86.
Apologies again for the breakage.
But yes, storage is coming!
@igorkofman you mean I wont have to do the below any longer???
<img width="271" alt="Image" src="https://github.com/user-attachments/assets/a3e73d80-a6a3-4e5a-9ecc-3eac51f1db43" />
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.