Settings

Configure every aspect of Suvadu through an interactive terminal UI — themes, exclusion patterns, auto-tags, and agent detection rules.

Quick Start

Launch the interactive settings TUI to browse and modify all configuration options.

suv settings

The TUI presents a tabbed interface where you can navigate between sections using arrow keys, edit values inline, and save changes on exit.

Settings Sections

Theme

Choose the visual theme for Suvadu's TUI components (search, stats, replay, settings). Themes control colors, borders, and highlight styles across all interactive views.

Exclusion Patterns

Define regex patterns for commands that should not be recorded. Any command matching an exclusion pattern is silently dropped before it reaches the database. Common patterns include:

^ls$ — skip bare ls calls
^cd — skip directory changes
^pwd$ — skip pwd
^clear$ — skip terminal clears
^exit$ — skip exit commands

Patterns use standard Rust regex syntax. Add as many as you need to keep your history clean and focused.

Auto-tags

Map directories to tags so that every session started in (or below) a directory is automatically tagged. For example:

~/work → Work
~/projects/api → API
~/dotfiles → Dotfiles

Auto-tags eliminate manual tagging. Combined with suv stats --tag and suv search --tag, they give you per-project analytics and search filtering automatically.

Agent Detection Rules

Configure how Suvadu identifies AI agent and IDE executor origins. Each rule consists of:

Name — a human-readable label (e.g., "Claude Code", "Cursor", "Aider").
Environment variable — the env var Suvadu checks to detect this agent (e.g., CLAUDE_CODE, CURSOR_SESSION_ID).
Executor type — one of agent, ide, or ci.

Several agents are pre-configured out of the box. Use this section to add detection rules for any custom or new AI tools you use.

Config File Locations

Suvadu stores its configuration in a TOML file. You can edit it directly if you prefer, though the TUI is recommended.

Platform	Config path
macOS	`~/Library/Application Support/suvadu/config.toml`
Linux	`~/.config/suvadu/config.toml`

Database Locations

Your shell history is stored in a local SQLite database with WAL mode for performance. The database is never synced or uploaded.

Platform	Database path
macOS	`~/Library/Application Support/suvadu/history.db`
Linux	`~/.local/share/suvadu/history.db`

Recording Control

Suvadu provides three commands to control whether commands are recorded to the database.

Enable recording

Turn recording on. This is the default state after installation.

suv enable

Disable recording

Turn recording off permanently until you re-enable it. No commands will be captured while disabled.

suv disable

Pause recording

Temporarily pause recording for the current shell session only. Recording resumes automatically when you open a new terminal. Useful when you need to run sensitive commands without logging them.

suv pause

Tip: Use suv pause before running commands that contain credentials or secrets you don't want in your history, even though Suvadu automatically redacts detected secrets.

How It Works

The suv settings TUI reads from and writes to the TOML config file. Changes take effect immediately — no restart required. The config file is human-readable and can be version-controlled or copied between machines. If the config file is missing, Suvadu creates one with sensible defaults on first run.