Database Warning Removal / Claude Code v0.2.107

Removed the persistent database unavailability warnings
Removed the /doctor command prompt for database issues
Removed better-sqlite3 troubleshooting messages and links
These changes suggest that database functionality has been stabilized or reimplemented

The build it came inv0.2.107

9 May 2025 · 7 entries, this one is #6.

Either side of it

Open the release →

Names in this entry

slash/doctor
Skill. Run a setup checkup that diagnoses issues and can fix them. Checks installation health, including duplicate or leftover installs, PATH problems, and unparseable settings files. Finds unused skills, MCP servers, and plugins versus their context cost, flags slow hooks, and checks for a newer version on your release channel. Deduplicates local CLAUDE.md files against checked-in ones, trims checked-in CLAUDE.md files by cutting content Claude could derive from the codebase, and migrates the always-loaded guidance that remains into skills and nested CLAUDE.md files that load on demand. Also offers to make auto mode your default and to pre-approve frequently denied read-only commands. Reports findings first and asks for confirmation before changing anything. From the terminal, claude doctor prints read-only installation diagnostics without starting a session. Alias: /checkup. Run /doctor prompt-audit to have Claude audit your CLAUDE.md files, skills, and other configuration for outdated or conflicting instructions instead of running the checkup. The prompt-audit subcommand requires Claude Code v2.1.283 or later. The CLAUDE.md trim check requires Claude Code v2.1.206 or later. Before v2.1.205, /doctor opened a read-only diagnostics screen and pressing f sent the report to Claude

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.