Troubleshooting
Collect logs, fix a corrupted local database and get help with the Hull Code extensions.
Collect logs in VS Code
Webview logs show errors from the Hull Code panel, including network and MCP problems.
- Open the Command Palette with
Cmd+Shift+P(macOS) orCtrl+Shift+P(Windows and Linux). - Run Developer: Open Webview Developer Tools.
- In the Console tab, clear the existing messages.
- Reproduce the problem.
- Look for errors, usually shown in red. For connection problems, also check the Network tab.
- Right-click in the console and choose Save as..., or copy the relevant errors.
Collect logs in JetBrains
Open Settings > Tools > Hull Code > Advanced. Under Diagnostic logs, open the client log, or download the backend log when you use remote development.
"database disk image is malformed"
If every prompt fails with SQLiteError: database disk image is malformed, Hull's local database may be corrupted. It stores local sessions and history.
Find the database
The database is hull.db in Hull's data directory:
| Platform | Path |
|---|---|
| macOS and Linux | ~/.local/share/hull/hull.db |
| Windows | %USERPROFILE%\.local\share\hull\hull.db |
| VS Code Remote SSH | ~/.local/share/hull/hull.db on the remote machine |
If you set XDG_DATA_HOME, the database is in $XDG_DATA_HOME/hull/ instead. With the Hull CLI installed, hull db path prints the exact location.
With VS Code Remote SSH, look on the remote machine, not your local computer.
Reset the database
Close your IDE or stop the Hull backend first. On macOS, Linux or Remote SSH:
pkill -f "hull serve"
mv ~/.local/share/hull/hull.db ~/.local/share/hull/hull.db.bak
mv ~/.local/share/hull/hull.db-wal ~/.local/share/hull/hull.db-wal.bak 2>/dev/null
mv ~/.local/share/hull/hull.db-shm ~/.local/share/hull/hull.db-shm.bak 2>/dev/nullOn Windows, rename hull.db and any hull.db-wal or hull.db-shm files in the same folder.
Restart your IDE or reconnect Remote SSH. Hull creates a new database the next time it starts.
This resets local sessions and history on that machine. Keep the .bak files if you want to share them with support or try to recover them later.
Reset all local Hull data
If a new database doesn't help, you can reset all local Hull data. This also removes local settings and cached files, so try the database reset first.
On macOS, Linux or Remote SSH, run this on the machine where Hull runs:
pkill -f "hull serve"
mv ~/.local/share/hull ~/.local/share/hull.bak 2>/dev/null
mv ~/.config/hull ~/.config/hull.bak 2>/dev/null
mv ~/.cache/hull ~/.cache/hull.bak 2>/dev/nullRestart your IDE or reconnect Remote SSH. Hull recreates these directories when it starts.
This resets local sessions, history, settings and cached data. Rename the directories rather than deleting them so you can recover files. Remove API keys and tokens before you share a backup with support.
Proxies and certificates
If Hull can't reach the network on a managed network, see Proxy and certificate settings for VS Code. The JetBrains plugin uses your IDE's proxy and certificate settings.
Contact support
If you still need help, email support@withhull.com with:
- The errors from the logs, with secrets removed
- Steps to reproduce the problem
- Screenshots or a screen recording, if you have them
- Your IDE version and Hull Code version