Settings

Launching

ait settings

The Settings TUI requires the shared Python virtual environment (installed by ait setup) with the textual and pyyaml packages.

Understanding the Layout

The Settings TUI organizes all configuration into four tabs, each accessible via a keyboard shortcut displayed in the footer.

Agent Defaults (a)

×

Shows the default agent/model for each operation (task-pick, explain, batch-review, raw). Each entry displays:

• The current value (e.g., claudecode/opus4_6)
• A layer badge: [PROJECT] (green) for project-level defaults or [USER] (amber) for per-user overrides
• A description of what the operation does

Press Enter on any operation to change its agent/model through a two-step picker.

Press d or Delete on an entry to remove a user override and revert to the project default.

Board (b)

Displays board configuration in two sections:

• Columns (read-only) – Lists each board column’s ID, title, and color
• User Settings (editable) – Auto-refresh (min) (cycle through 0, 1, 2, 5, 10, 15, 30 where 0 = disabled) and Sync on refresh (toggle whether push/pull runs on each auto-refresh)

Press Save Board Settings to persist changes.

Models (m)

Read-only display of all available models organized by agent (claudecode, codex, geminicli, opencode). For each model, shows:

• Name – Internal identifier used in agent strings
• CLI ID – Exact model ID passed to the CLI
• Notes – Description of the model
• Verification scores – Per-operation scores (task-pick, explain, batch-review)

Model definitions are managed by editing aitasks/metadata/models_<agent>.json files directly or using the /aitask-refresh-code-models skill.

Profiles (p)

Browse and edit execution profiles – YAML files that pre-answer workflow questions to reduce interactive prompts. Each profile contains settings organized into groups:

• Identity – name, description
• Task Selection – skip_task_confirmation, default_email
• Branch & Worktree – create_worktree, base_branch
• Planning – plan_preference, plan_preference_child, post_plan_action
• Exploration – explore_auto_continue
• Lock Management – force_unlock_stale
• Remote Workflow – done_task_action, orphan_parent_action, complexity_action, review_action, issue_action, abort_plan_action, abort_revert_status

Fields use type-appropriate controls: boolean keys toggle between true/false/(unset), enum keys cycle through their options, and string keys open an edit dialog. Setting a value to (unset) removes it from the profile so the question is asked interactively at runtime.

Navigating