Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
docs: consolidate configuration into config command help
Maximilian Roos81f46093d183
diff --git a/docs/content/config.md b/docs/content/config.mdindex 85a179907..2fc892550 100644--- a/docs/content/config.md+++ b/docs/content/config.md@@ -8,7 +8,14 @@ group = "Commands"<!-- ⚠️ AUTO-GENERATED from `wt config --help-page` — edit src/cli.rs to update -->-Manages configuration, shell integration, and runtime settings. The command provides subcommands for setup, inspection, and cache management.+Manages configuration, shell integration, and runtime settings.++Worktrunk uses two configuration files:++| File | Location | Purpose |+|------|----------|---------|+| **User config** | `~/.config/worktrunk/config.toml` | Personal settings, command defaults, approved project commands |+| **Project config** | `.config/wt.toml` | Lifecycle hooks, checked into version control |## Examples@@ -30,11 +37,117 @@ Show current configuration and file locations:wt config show```+## User config++The user config stores personal preferences that apply across all repositories. Create it with `wt config create` and view with `wt config show`.++### Worktree path template++Controls where new worktrees are created. The template is relative to the repository root.++**Available variables:**+- `{{ main_worktree }}` — main worktree directory name+- `{{ branch }}` — branch name (slashes replaced with dashes)++**Examples** for a repo at `~/code/myproject` creating branch `feature/login`:++```toml+# Default — siblings in parent directory+# Creates: ~/code/myproject.feature-login+worktree-path = "../{{ main_worktree }}.{{ branch }}"++# Inside the repository+# Creates: ~/code/myproject/.worktrees/feature-login+worktree-path = ".worktrees/{{ branch }}"++# Namespaced (useful when multiple repos share a parent directory)+# Creates: ~/code/worktrees/myproject/feature-login+worktree-path = "../worktrees/{{ main_worktree }}/{{ branch }}"+```++### Command defaults++Override default flag behavior for commands. Settings here apply unless explicitly overridden on the command line.++**`wt list` defaults:**++```toml+[list]+full = true # --full (default: false)+branches = true # --branches (default: false)+remotes = true # --remotes (default: false)+```++**`wt step commit` and `wt merge` staging:**++```toml+[commit]+stage = "all" # "all" (default), "tracked", or "none"+```++**`wt merge` defaults:**++```toml+[merge]+# All options default to true+squash = false # --no-squash: preserve individual commits+commit = false # --no-commit: skip committing uncommitted changes+remove = false # --no-remove: keep worktree after merge+verify = false # --no-verify: skip project hooks+```++### LLM commit messages++Configure automatic commit message generation. Requires an external tool like [llm](https://llm.datasette.io/):++```toml+[commit-generation]+command = "llm"+args = ["-m", "claude-haiku-4.5"]+```++See [LLM Commit Messages](@/llm-commits.md) for setup details and template customization.++### Approved commands++When project hooks run for the first time, Worktrunk prompts for approval. Approved commands are saved here automatically:++```toml+[projects."my-project"]+approved-commands = [+ "post-create.install = npm ci",+ "pre-merge.test = npm test",+]+```++Manage approvals with `wt config approvals list` and `wt config approvals clear <repo>`.++## Project config++The project config defines lifecycle hooks — commands that run at specific points during worktree operations. This file is checked into version control and shared across the team.++Create `.config/wt.toml` in the repository root:++```toml+[post-create]+install = "npm ci"++[pre-merge]+test = "npm test"+lint = "npm run lint"+```++See [Hooks](@/hooks.md) for complete documentation on hook types, execution order, and template variables.+## Shell integration-Shell integration allows Worktrunk to change the shell's working directory after `wt switch`. Without it, commands run in a subprocess and directory changes don't persist.+Worktrunk needs shell integration to change directories when switching worktrees. Install with:++```bash+wt config shell install+```-The `wt config shell install` command adds integration to the shell's config file. Manual installation:+Or manually add to the shell config:```bash# For bash: add to ~/.bashrc@@ -47,37 +160,51 @@ eval "$(wt config shell init zsh)"wt config shell init fish | source```-## Configuration files+Without shell integration, `wt switch` prints the target directory but cannot `cd` into it.++## Environment variables++All user config options can be overridden with environment variables using the `WORKTRUNK_` prefix.-**User config** — `~/.config/worktrunk/config.toml` (or `$WORKTRUNK_CONFIG_PATH`):+### Naming convention-Personal settings like LLM commit generation, path templates, and default behaviors. The `wt config create` command generates a file with documented examples.+Config keys use kebab-case (`worktree-path`), while env vars use SCREAMING_SNAKE_CASE (`WORKTRUNK_WORKTREE_PATH`). The conversion happens automatically.-**Project config** — `.config/wt.toml` in repository root:+For nested config sections, use double underscores to separate levels:-Project-specific hooks: post-create, post-start, pre-commit, pre-merge, post-merge. See [Hooks](@/hooks.md) for details.+| Config | Environment Variable |+|--------|---------------------|+| `worktree-path` | `WORKTRUNK_WORKTREE_PATH` |+| `commit-generation.command` | `WORKTRUNK_COMMIT_GENERATION__COMMAND` |+| `commit-generation.args` | `WORKTRUNK_COMMIT_GENERATION__ARGS` |-## Command approvals+Note the single underscore after `WORKTRUNK` and double underscores between nested keys.-Project hooks require approval on first run. Manage saved approvals with:+### Array values++Array config values like `args = ["-m", "claude-haiku"]` can be specified as a single string in environment variables:```bash-wt config approvals list # Show all approved commands-wt config approvals clear <repo> # Remove approvals for a repository+export WORKTRUNK_COMMIT_GENERATION__ARGS="-m claude-haiku"```-See [Hooks](@/hooks.md#security--approval) for how approvals work.--## LLM commit messages+### Example: CI/testing override-Worktrunk can generate commit messages using an LLM. Enable in user config:+Override the LLM command in CI to use a mock:-```toml-[commit-generation]-command = "llm"+```bash+WORKTRUNK_COMMIT_GENERATION__COMMAND=echo \+WORKTRUNK_COMMIT_GENERATION__ARGS="test: automated commit" \+ wt merge```-See [LLM Commits](@/llm-commits.md) for installation, provider setup, and customization.+### Special variables++| Variable | Purpose |+|----------|---------|+| `WORKTRUNK_CONFIG_PATH` | Override user config file location (not a config key) |+| `NO_COLOR` | Disable colored output ([standard](https://no-color.org/)) |+| `CLICOLOR_FORCE` | Force colored output even when not a TTY |---diff --git a/docs/content/configuration.md b/docs/content/configuration.mddeleted file mode 100644index 58921e99a..000000000--- a/docs/content/configuration.md+++ /dev/null@@ -1,175 +0,0 @@-+++-title = "Configuration"-weight = 20--[extra]-group = "Reference"-+++--Worktrunk uses two configuration files:--| File | Location | Purpose |-|------|----------|---------|-| **User config** | `~/.config/worktrunk/config.toml` | Personal settings, command defaults, approved project commands |-| **Project config** | `.config/wt.toml` | Lifecycle hooks, checked into version control |--## Shell integration--Worktrunk needs shell integration to change directories when switching worktrees. Install with `wt config shell install`. See [wt config](@/config.md#shell-integration) for manual installation options.--## User config--The user config stores personal preferences that apply across all repositories. Create it with:--```bash-wt config create-```--This creates `~/.config/worktrunk/config.toml` with documented examples. View the current configuration with `wt config show`.--### Worktree path template--Controls where new worktrees are created. The template is relative to the repository root:--```toml-# Default — siblings in parent directory-worktree-path = "../{{ main_worktree }}.{{ branch }}"--# Inside the repository-worktree-path = ".worktrees/{{ branch }}"--# Namespaced (useful when multiple repos share a parent directory)-worktree-path = "../worktrees/{{ main_worktree }}/{{ branch }}"-```--**Available variables:**-- `{{ main_worktree }}` — main worktree directory name-- `{{ branch }}` — branch name (slashes replaced with dashes)--### Command defaults--Override default flag behavior for commands. Settings here apply unless explicitly overridden on the command line.--**`wt list` defaults:**--```toml-[list]-full = true # --full (default: false)-branches = true # --branches (default: false)-remotes = true # --remotes (default: false)-```--**`wt step commit` and `wt merge` staging:**--```toml-[commit]-stage = "all" # "all" (default), "tracked", or "none"-```--**`wt merge` defaults:**--```toml-[merge]-# All options default to true-squash = false # --no-squash: preserve individual commits-commit = false # --no-commit: skip committing uncommitted changes-remove = false # --no-remove: keep worktree after merge-verify = false # --no-verify: skip project hooks-```--### LLM commit messages--Configure automatic commit message generation. Requires an external tool like [llm](https://llm.datasette.io/):--```toml-[commit-generation]-command = "llm"-args = ["-m", "claude-haiku-4.5"]--# Optional: custom prompt templates (inline or from files)-template = "Write a commit message for: {{ git_diff }}"-squash-template = "Summarize these commits: {{ commits }}"-template-file = "~/.config/worktrunk/commit.txt"-squash-template-file = "~/.config/worktrunk/squash.txt"-```--See [LLM Commit Messages](@/llm-commits.md) for setup details and template variables.--### Approved commands--When project hooks run for the first time, Worktrunk prompts for approval. Approved commands are saved here automatically:--```toml-[projects."my-project"]-approved-commands = [- "post-create.install = npm ci",- "pre-merge.test = npm test",-]-```--Manage approvals with `wt config approvals list` and `wt config approvals clear <repo>`.--### Statusline--`wt list statusline` outputs a compact single-line status for shell prompts or editor statuslines. See [Claude Code Integration](@/claude-code.md#statusline) for Claude Code configuration.--## Project config--The project config defines lifecycle hooks — commands that run at specific points during worktree operations. This file is checked into version control and shared across the team.--Create `.config/wt.toml` in the repository root:--```toml-[post-create]-install = "npm ci"--[pre-merge]-test = "npm test"-lint = "npm run lint"-```--See [Hooks](@/hooks.md) for complete documentation on hook types, execution order, and template variables.--## Environment variables--All user config options can be overridden with environment variables using the `WORKTRUNK_` prefix.--### Naming convention--Config keys use kebab-case (`worktree-path`), while env vars use SCREAMING_SNAKE_CASE (`WORKTRUNK_WORKTREE_PATH`). The conversion happens automatically.--For nested config sections, use double underscores to separate levels:--| Config | Environment Variable |-|--------|---------------------|-| `worktree-path` | `WORKTRUNK_WORKTREE_PATH` |-| `commit-generation.command` | `WORKTRUNK_COMMIT_GENERATION__COMMAND` |-| `commit-generation.args` | `WORKTRUNK_COMMIT_GENERATION__ARGS` |--Note the single underscore after `WORKTRUNK` and double underscores between nested keys.--### Array values--Array config values like `args = ["-m", "claude-haiku"]` can be specified as a single string in environment variables:--```bash-export WORKTRUNK_COMMIT_GENERATION__ARGS="-m claude-haiku"-```--### Example: CI/testing override--Override the LLM command in CI to use a mock:--```bash-WORKTRUNK_COMMIT_GENERATION__COMMAND=echo \-WORKTRUNK_COMMIT_GENERATION__ARGS="test: automated commit" \- wt merge-```--### Special variables--| Variable | Purpose |-|----------|---------|-| `WORKTRUNK_CONFIG_PATH` | Override user config file location (not a config key) |-| `NO_COLOR` | Disable colored output ([standard](https://no-color.org/)) |-| `CLICOLOR_FORCE` | Force colored output even when not a TTY |diff --git a/src/cli.rs b/src/cli.rsindex a1b4a5ec4..25ca53fde 100644--- a/src/cli.rs+++ b/src/cli.rs@@ -663,7 +663,14 @@ pub enum Commands {/// Manage configuration and shell integration#[command(about = "Manage configuration and shell integration",- after_long_help = r#"Manages configuration, shell integration, and runtime settings. The command provides subcommands for setup, inspection, and cache management.+ after_long_help = r#"Manages configuration, shell integration, and runtime settings.++Worktrunk uses two configuration files:++| File | Location | Purpose |+|------|----------|---------|+| **User config** | `~/.config/worktrunk/config.toml` | Personal settings, command defaults, approved project commands |+| **Project config** | `.config/wt.toml` | Lifecycle hooks, checked into version control |## Examples@@ -685,11 +692,117 @@ Show current configuration and file locations:wt config show```+## User config++The user config stores personal preferences that apply across all repositories. Create it with `wt config create` and view with `wt config show`.++### Worktree path template++Controls where new worktrees are created. The template is relative to the repository root.++**Available variables:**+- `{{ main_worktree }}` — main worktree directory name+- `{{ branch }}` — branch name (slashes replaced with dashes)++**Examples** for a repo at `~/code/myproject` creating branch `feature/login`:++```toml+# Default — siblings in parent directory+# Creates: ~/code/myproject.feature-login+worktree-path = "../{{ main_worktree }}.{{ branch }}"++# Inside the repository+# Creates: ~/code/myproject/.worktrees/feature-login+worktree-path = ".worktrees/{{ branch }}"++# Namespaced (useful when multiple repos share a parent directory)+# Creates: ~/code/worktrees/myproject/feature-login+worktree-path = "../worktrees/{{ main_worktree }}/{{ branch }}"+```++### Command defaults++Override default flag behavior for commands. Settings here apply unless explicitly overridden on the command line.++**`wt list` defaults:**++```toml+[list]+full = true # --full (default: false)+branches = true # --branches (default: false)+remotes = true # --remotes (default: false)+```++**`wt step commit` and `wt merge` staging:**++```toml+[commit]+stage = "all" # "all" (default), "tracked", or "none"+```++**`wt merge` defaults:**++```toml+[merge]+# All options default to true+squash = false # --no-squash: preserve individual commits+commit = false # --no-commit: skip committing uncommitted changes+remove = false # --no-remove: keep worktree after merge+verify = false # --no-verify: skip project hooks+```++### LLM commit messages++Configure automatic commit message generation. Requires an external tool like [llm](https://llm.datasette.io/):++```toml+[commit-generation]+command = "llm"+args = ["-m", "claude-haiku-4.5"]+```++See [LLM Commit Messages](@/llm-commits.md) for setup details and template customization.++### Approved commands++When project hooks run for the first time, Worktrunk prompts for approval. Approved commands are saved here automatically:++```toml+[projects."my-project"]+approved-commands = [+ "post-create.install = npm ci",+ "pre-merge.test = npm test",+]+```++Manage approvals with `wt config approvals list` and `wt config approvals clear <repo>`.++## Project config++The project config defines lifecycle hooks — commands that run at specific points during worktree operations. This file is checked into version control and shared across the team.++Create `.config/wt.toml` in the repository root:++```toml+[post-create]+install = "npm ci"++[pre-merge]+test = "npm test"+lint = "npm run lint"+```++See [Hooks](@/hooks.md) for complete documentation on hook types, execution order, and template variables.+## Shell integration-Shell integration allows Worktrunk to change the shell's working directory after `wt switch`. Without it, commands run in a subprocess and directory changes don't persist.+Worktrunk needs shell integration to change directories when switching worktrees. Install with:++```console+wt config shell install+```-The `wt config shell install` command adds integration to the shell's config file. Manual installation:+Or manually add to the shell config:```console# For bash: add to ~/.bashrc@@ -702,37 +815,51 @@ eval "$(wt config shell init zsh)"wt config shell init fish | source```-## Configuration files+Without shell integration, `wt switch` prints the target directory but cannot `cd` into it.++## Environment variables++All user config options can be overridden with environment variables using the `WORKTRUNK_` prefix.++### Naming convention-**User config** — `~/.config/worktrunk/config.toml` (or `$WORKTRUNK_CONFIG_PATH`):+Config keys use kebab-case (`worktree-path`), while env vars use SCREAMING_SNAKE_CASE (`WORKTRUNK_WORKTREE_PATH`). The conversion happens automatically.-Personal settings like LLM commit generation, path templates, and default behaviors. The `wt config create` command generates a file with documented examples.+For nested config sections, use double underscores to separate levels:-**Project config** — `.config/wt.toml` in repository root:+| Config | Environment Variable |+|--------|---------------------|+| `worktree-path` | `WORKTRUNK_WORKTREE_PATH` |+| `commit-generation.command` | `WORKTRUNK_COMMIT_GENERATION__COMMAND` |+| `commit-generation.args` | `WORKTRUNK_COMMIT_GENERATION__ARGS` |-Project-specific hooks: post-create, post-start, pre-commit, pre-merge, post-merge. See [Hooks](@/hooks.md) for details.+Note the single underscore after `WORKTRUNK` and double underscores between nested keys.-## Command approvals+### Array values-Project hooks require approval on first run. Manage saved approvals with:+Array config values like `args = ["-m", "claude-haiku"]` can be specified as a single string in environment variables:```console-wt config approvals list # Show all approved commands-wt config approvals clear <repo> # Remove approvals for a repository+export WORKTRUNK_COMMIT_GENERATION__ARGS="-m claude-haiku"```-See [Hooks](@/hooks.md#security--approval) for how approvals work.+### Example: CI/testing override-## LLM commit messages+Override the LLM command in CI to use a mock:-Worktrunk can generate commit messages using an LLM. Enable in user config:--```toml-[commit-generation]-command = "llm"+```console+WORKTRUNK_COMMIT_GENERATION__COMMAND=echo \+WORKTRUNK_COMMIT_GENERATION__ARGS="test: automated commit" \+ wt merge```-See [LLM Commits](@/llm-commits.md) for installation, provider setup, and customization.+### Special variables++| Variable | Purpose |+|----------|---------|+| `WORKTRUNK_CONFIG_PATH` | Override user config file location (not a config key) |+| `NO_COLOR` | Disable colored output ([standard](https://no-color.org/)) |+| `CLICOLOR_FORCE` | Force colored output even when not a TTY |"#)]Config {diff --git a/tests/integration_tests/readme_sync.rs b/tests/integration_tests/readme_sync.rsindex 6c4c9568f..e6cd2729f 100644--- a/tests/integration_tests/readme_sync.rs+++ b/tests/integration_tests/readme_sync.rs@@ -923,7 +923,6 @@ fn test_docs_quickstart_examples_are_in_sync() {// Process all docs files with AUTO-GENERATED-HTML markerslet doc_files = ["docs/content/quickstart.md",- "docs/content/configuration.md","docs/content/concepts.md","docs/content/advanced.md",];diff --git a/tests/snapshots/integration__integration_tests__help__help_config_long.snap b/tests/snapshots/integration__integration_tests__help__help_config_long.snapindex a043e22af..430c371ba 100644--- a/tests/snapshots/integration__integration_tests__help__help_config_long.snap+++ b/tests/snapshots/integration__integration_tests__help__help_config_long.snap@@ -42,7 +42,14 @@ Usage: [1m[36mwt config[0m [36m[OPTIONS][0m [36m<COMMAND>[0m[1m[36m-v[0m, [1m[36m--verbose[0mShow commands and debug info-Manages configuration, shell integration, and runtime settings. The command provides subcommands for setup, inspection, and cache management.+Manages configuration, shell integration, and runtime settings.++Worktrunk uses two configuration files:++| File | Location | Purpose |+|------|----------|---------|+| [1mUser config[0m | [2m~/.config/worktrunk/config.toml[0m | Personal settings, command defaults, approved project commands |+| [1mProject config[0m | [2m.config/wt.toml[0m | Lifecycle hooks, checked into version control |[32mExamples[0m@@ -58,11 +65,101 @@ Show current configuration and file locations:[2mwt config show[0m+[32mUser config[0m++The user config stores personal preferences that apply across all repositories. Create it with [2mwt config create[0m and view with [2mwt config show[0m.++[1mWorktree path template[0m++Controls where new worktrees are created. The template is relative to the repository root.++[1mAvailable variables:[0m+- [2m{{ main_worktree }}[0m — main worktree directory name+- [2m{{ branch }}[0m — branch name (slashes replaced with dashes)++[1mExamples[0m for a repo at [2m~/code/myproject[0m creating branch [2mfeature/login[0m:++ [2m# Default — siblings in parent directory[0m+ [2m# Creates: ~/code/myproject.feature-login[0m+ [2mworktree-path = "../{{ main_worktree }}.{{ branch }}"[0m+ [2m[0m+ [2m# Inside the repository[0m+ [2m# Creates: ~/code/myproject/.worktrees/feature-login[0m+ [2mworktree-path = ".worktrees/{{ branch }}"[0m+ [2m[0m+ [2m# Namespaced (useful when multiple repos share a parent directory)[0m+ [2m# Creates: ~/code/worktrees/myproject/feature-login[0m+ [2mworktree-path = "../worktrees/{{ main_worktree }}/{{ branch }}"[0m++[1mCommand defaults[0m++Override default flag behavior for commands. Settings here apply unless explicitly overridden on the command line.++[1m`wt list` defaults:[0m++ [2m[list][0m+ [2mfull = true # --full (default: false)[0m+ [2mbranches = true # --branches (default: false)[0m+ [2mremotes = true # --remotes (default: false)[0m++[1m`wt step commit` and `wt merge` staging:[0m++ [2m[commit][0m+ [2mstage = "all" # "all" (default), "tracked", or "none"[0m++[1m`wt merge` defaults:[0m++ [2m[merge][0m+ [2m# All options default to true[0m+ [2msquash = false # --no-squash: preserve individual commits[0m+ [2mcommit = false # --no-commit: skip committing uncommitted changes[0m+ [2mremove = false # --no-remove: keep worktree after merge[0m+ [2mverify = false # --no-verify: skip project hooks[0m++[1mLLM commit messages[0m++Configure automatic commit message generation. Requires an external tool like llm:++ [2m[commit-generation][0m+ [2mcommand = "llm"[0m+ [2margs = ["-m", "claude-haiku-4.5"][0m++See LLM Commit Messages for setup details and template customization.++[1mApproved commands[0m++When project hooks run for the first time, Worktrunk prompts for approval. Approved commands are saved here automatically:++ [2m[projects."my-project"][0m+ [2mapproved-commands = [[0m+ [2m "post-create.install = npm ci",[0m+ [2m "pre-merge.test = npm test",[0m+ [2m][0m++Manage approvals with [2mwt config approvals list[0m and [2mwt config approvals clear <repo>[0m.++[32mProject config[0m++The project config defines lifecycle hooks — commands that run at specific points during worktree operations. This file is checked into version control and shared across the team.++Create [2m.config/wt.toml[0m in the repository root:++ [2m[post-create][0m+ [2minstall = "npm ci"[0m+ [2m[0m+ [2m[pre-merge][0m+ [2mtest = "npm test"[0m+ [2mlint = "npm run lint"[0m++See Hooks for complete documentation on hook types, execution order, and template variables.+[32mShell integration[0m-Shell integration allows Worktrunk to change the shell's working directory after [2mwt switch[0m. Without it, commands run in a subprocess and directory changes don't persist.+Worktrunk needs shell integration to change directories when switching worktrees. Install with:++ [2mwt config shell install[0m-The [2mwt config shell install[0m command adds integration to the shell's config file. Manual installation:+Or manually add to the shell config:[2m# For bash: add to ~/.bashrc[0m[2meval "$(wt config shell init bash)"[0m@@ -73,30 +170,44 @@ The [2mwt config shell install[0m command adds integration to the shell's conf[2m# For fish: add to ~/.config/fish/config.fish[0m[2mwt config shell init fish | source[0m-[32mConfiguration files[0m+Without shell integration, [2mwt switch[0m prints the target directory but cannot [2mcd[0m into it.-[1mUser config[0m — [2m~/.config/worktrunk/config.toml[0m (or [2m$WORKTRUNK_CONFIG_PATH[0m):+[32mEnvironment variables[0m-Personal settings like LLM commit generation, path templates, and default behaviors. The [2mwt config create[0m command generates a file with documented examples.+All user config options can be overridden with environment variables using the [2mWORKTRUNK_[0m prefix.-[1mProject config[0m — [2m.config/wt.toml[0m in repository root:+[1mNaming convention[0m-Project-specific hooks: post-create, post-start, pre-commit, pre-merge, post-merge. See Hooks for details.+Config keys use kebab-case ([2mworktree-path[0m), while env vars use SCREAMING_SNAKE_CASE ([2mWORKTRUNK_WORKTREE_PATH[0m). The conversion happens automatically.-[32mCommand approvals[0m+For nested config sections, use double underscores to separate levels:-Project hooks require approval on first run. Manage saved approvals with:+| Config | Environment Variable |+|--------|---------------------|+| [2mworktree-path[0m | [2mWORKTRUNK_WORKTREE_PATH[0m |+| [2mcommit-generation.command[0m | [2mWORKTRUNK_COMMIT_GENERATION__COMMAND[0m |+| [2mcommit-generation.args[0m | [2mWORKTRUNK_COMMIT_GENERATION__ARGS[0m |- [2mwt config approvals list # Show all approved commands[0m- [2mwt config approvals clear <repo> # Remove approvals for a repository[0m+Note the single underscore after [2mWORKTRUNK[0m and double underscores between nested keys.-See Hooks for how approvals work.+[1mArray values[0m-[32mLLM commit messages[0m+Array config values like [2margs = ["-m", "claude-haiku"][0m can be specified as a single string in environment variables:-Worktrunk can generate commit messages using an LLM. Enable in user config:+ [2mexport WORKTRUNK_COMMIT_GENERATION__ARGS="-m claude-haiku"[0m- [2m[commit-generation][0m- [2mcommand = "llm"[0m+[1mExample: CI/testing override[0m++Override the LLM command in CI to use a mock:++ [2mWORKTRUNK_COMMIT_GENERATION__COMMAND=echo \[0m+ [2mWORKTRUNK_COMMIT_GENERATION__ARGS="test: automated commit" \[0m+ [2m wt merge[0m++[1mSpecial variables[0m-See LLM Commits for installation, provider setup, and customization.+| Variable | Purpose |+|----------|---------|+| [2mWORKTRUNK_CONFIG_PATH[0m | Override user config file location (not a config key) |+| [2mNO_COLOR[0m | Disable colored output (standard) |+| [2mCLICOLOR_FORCE[0m | Force colored output even when not a TTY |