Module settings 

Wisp settings management and theme loading.

Wisp has two tiers of configuration:

1. Wisp settings — persisted in ~/.wisp/settings.json (or $WISP_HOME/settings.json). Controls UI preferences via WispSettings, including theme, content padding, and status-line segments.
2. Agent settings — model, reasoning effort, MCP servers, etc. These are advertised by the agent over ACP and edited through the in-app SettingsOverlay.

Theme resolution

1. load_or_create_settings reads (or creates) the settings file.
2. load_theme checks ThemeSettings::file for a .tmTheme filename.
3. resolve_theme_file_path validates the filename (must be a bare basename, no path traversal) and resolves it to ~/.wisp/themes/<name>.
4. tui::Theme::load_from_path parses the file, falling back to the default theme on error.

Status-line resolution

1. resolve_status_line_settings resolves optional StatusLineSettings from the Wisp settings file.
2. Launchers provide the default StatusLineSettings to use when no status-line settings are present; standalone Wisp includes the agent segment, while Aether-backed launches omit it unless configured explicitly.

Modules

menu

overlay

types

Structs

ResolvedStatusLineSettings

StatusLineSettings

ThemeSettings

WispSettings

Enums

StatusLineSegmentConfig

StatusLineStyle

Constants

DEFAULT_CONTENT_PADDING

Functions

list_theme_files

load_or_create_settings

load_theme

resolve_content_padding

resolve_status_line_settings

resolve_theme_file_path

save_settings

themes_dir_path

wisp_home