Resetting settings and state

If Solo is behaving unexpectedly, you don't need to nuke everything. Start by resetting only the part that's likely broken.

Reset hotkeys only#

1. Open Settings > Hotkeys.
2. Click Reset All.
3. In the Reset all shortcuts? dialog, click Reset all.

That's all you need if only your key bindings are messed up.

Reset all core app data#

Solo's core app-data directory defaults to:

~/.config/soloterm/

If SOLOTERM_APP_DATA_DIR is set, that override is used instead. This core directory contains the primary solo.db database plus agent-channels.db, which stores scratchpads, todos, comments, coordination records, and related agent-channel state.

To fully reset core state:

1. Quit Solo completely.
2. Move the directory aside so you have a backup:

mv ~/.config/soloterm ~/.config/soloterm.backup

3. Launch Solo again. It creates fresh core databases.

This resets projects, command records, trust state, agent-channel state, and other data in that core directory.

Reset window placement files#

Solo does not currently expose a supported built-in window reset, and window state is not all stored in the core directory above:

• Solo's window-state layer resolves its state file through the platform-managed application-config directory for bundle identifier com.soloterm.solo.
• .display-snapshot.json resolves through the platform-managed application-data directory for the same bundle. Separate startup compatibility code also looks for .window-state.json in that application-data scope.
• Main and workspace-window position and size are stored in the workspace_window_groups setting in solo.db.

Do not treat ~/.config/soloterm/.window-state.json and ~/.config/soloterm/.display-snapshot.json as a standalone window reset. Deleting auxiliary JSON files does not reset main/workspace geometry. With the source-backed procedures documented here, resetting that geometry requires the full core-state reset above, which resets all solo.db state; move the directory aside first.

Reset only the primary database#

To isolate the primary database without moving the full core directory:

mv ~/.config/soloterm/solo.db ~/.config/soloterm/solo.db.backup

Then relaunch Solo. This isolates solo.db only; it does not replace agent-channels.db, browser-persisted UI preferences, or platform window-state files. If Solo starts, the previous primary database was likely damaged.

Notes#

• There aren't any built-in command-palette actions today for full reset or window reset.
• UI-only preferences such as theme, sidebar widths, and terminal font settings are persisted in browser storage under solo-ui-storage, so deleting only solo.db isn't always a full visual reset.