worktrunk

Release Notes

Improved

• wt list and the wt switch picker settle faster in repos with many worktrees: rows fill from the top down, and on macOS with core.fsmonitor=true no daemon start is forked for a worktree whose daemon is already running. On a 50-worktree repo the picker's per-row work starts at 47ms, down from 120ms. (#4286, #4290, #4288, #4284)

• CI status skips branches that were never pushed: wt list --full, the picker, and the statusline no longer query the forge for a local branch no remote has, so a repo with 239 local branches made 25 gh calls instead of 249. A PR opened from a branch another clone pushed shows once you fetch. GitLab looks up its project ID once per command, not per row. (#4289, #4216)

• Leaner Codex commit generation: the recommended Codex command moves to gpt-6-luna with reasoning off and unneeded Codex features disabled, so each message sends fewer input tokens. Accepting the first-run Codex prompt now also creates ~/.codex/worktrunk-commit-instructions.txt, which the command reads. Docs (#4261)

• Releases ship a signed packslip: each GitHub release includes packslip.sigstore.json, a manifest of the archives' digests, platforms, completions, and agent skills, signed by the release workflow so installers such as mise can verify downloads before unpacking. (#4301, thanks @jdx)

Fixed

• A squash whose commit fails keeps the branch: when a git commit hook or signing stopped the commit in wt merge or wt step squash, the branch was left at the merge base with its changes staged, recoverable from the reflog. Now the branch is untouched. (Breaking: git commit hooks run on a detached HEAD during a squash.) (#4206, thanks @Bennyjitsu for finding it in #4193)

• wt step diff when local main lags origin/main: for a branch built on the newer origin/main, the diff included the upstream commits in between. It now uses the same base as wt merge. (#4281, thanks @starlightromero, whose #3519 reported the same case for wt merge)

• Submodules with an ignore setting: when submodule.<name>.ignore or diff.ignoreSubmodules hid uncommitted changes inside a submodule, wt remove and wt step prune read the worktree as clean and removed it along with them; they now keep it. With ignore=all, wt step commit and squashes now commit a staged submodule pointer instead of leaving it staged. (#4252, #4192, #4206, #4303, thanks @Duang777)

• Worktrees whose .git was deleted but whose directory remains (macOS $TMPDIR cleanup can do this): wt remove <branch> failed, and wt step prune skipped or errored on them. Both now unregister the worktree and leave its files; one with staged changes or an operation in progress is kept by wt step prune, and refused by wt remove without --force. (#4228, #4226, #4302)

• wt merge --no-squash with a stage mode that stages nothing: with --stage=none and only unstaged changes

Release Notes

Improved

• wt switch --no-cd -x <program> runs the program in the worktree: it started in the invoking directory, so a program meant for the new worktree had to be handed {{ worktree_path }}. --no-cd now governs only your shell — wt switch feature --no-cd -x code -- . opens the worktree in an editor and leaves your terminal put. (Breaking: a program that wanted the invoking directory needs an explicit cd.) Fixes #4042. (#4179, thanks @yajo for reporting)

• The picker's preview tabs show which have content: a tab's label is dim when that tab is empty for the selected row, and underlined when it's the active tab. Availability sat on the tab's number alone, so every inactive label read dim whatever the row held. (#4174)

• Messages name the destination, and end with the command to run: without shell integration, wt merge and wt remove printed Cannot change directory — shell integration not installed and no path; the warning now names the worktree, as wt switch already did. "Cannot determine default branch" had three wordings, and three recovery hints put their command first rather than last. (#4163, #4155, thanks @blrain3 for reporting)

• /wt-switch-create no longer stalls at Claude Code's path-entry dialog: Claude Code confirms every entry outside .claude/worktrees/, which is every Worktrunk worktree, so a background session waited for someone to attach. The plugin now approves entry into a worktree at its worktree-path location, and reads a bare name as the repo or the branch. (#4158, #4159)

• wt config update --output accepts the config being migrated: it refused that path when the migration dropped approved-commands. Those approvals now move to approvals.toml first, exactly as the in-place update moves them. (#4204)

Fixed

• wt merge on a dirty worktree describes what it commits: the generated message covered the branch's earlier commits and said nothing about the work the merge had just staged into the same commit. wt step squash --dry-run now previews what the run would commit, as wt step commit --dry-run does. (#4178)

• A config save no longer rewrites the rest of your config: declining a prompt, or setting the commit-generation command, rewrote the whole file, dropping values written at their default and re-spelling hook pipelines and dropping their comments. It also reloaded that file over the in-memory config, so wt step commit --config-set 'commit.stage="none"' staged everything once it had asked about commit generation. (#4160, #4156, #4151)

• Diff display config no longer reaches Worktrunk's prompts or its integration check: color.ui = always and diff.external reached the commit, squash, and summary prompts. Two corner cases also made wt remove and wt step prune delete an unmerged branch: diff.relative set and a Worktrunk command run from a subdirectory the branch's changes sat entirely outside, or submodule.<name>.ignore = all (git config or .gitmodules) and a submodule bump as its only change. (#4146, #4147)

• Auto-staging names a wholly untracked directory once: since 0.78.0 the warning expanded each one into its files, so wt step commit, wt step squash, and wt merge lis

Release Notes

Improved

• Hook scripts read renamed context keys: the JSON piped to every hook drops worktree, repo_root, main_worktree, and main_worktree_path in favour of worktree_path, repo_path, repo, and primary_worktree_path. Config templates migrate on load, so hooks written with the old names keep working; scripts reading the JSON, --execute templates, and --var overrides need updating. (Breaking.) (#4080)

• wt config plugins pi installs for Pi; oh-my-pi moves to wt config plugins omp: pi install wrote an oh-my-pi hook, which Pi never loads; Pi users re-run it to get a Pi extension. Existing oh-my-pi hooks keep working, listed as outdated until wt config plugins omp install. (Breaking: scripts that run wt config plugins pi for oh-my-pi need omp.) Docs (#4135, thanks @ashebanow)

• Interactive prompts no longer open with a blank line: wt config shell install, wt config plugins claude install, and the commit-message setup offer in wt merge began with one. (#4059)

• wt config show gives a single wt config shell install hint: an outdated wrapper, a fish wrapper at the deprecated conf.d path, and missing fish completions each printed their own hint. The zsh compinit snippet is now syntax-highlighted. (#4059)

• wt config update --output <path> confirms the write: it now prints ✓ Wrote user config migration @ ~/migrated.toml where it printed nothing. --output=- stays silent. (#4053)

Fixed

• Removal no longer discards untracked files hidden by status.showUntrackedFiles = no: under that setting, a worktree holding only untracked files looked clean, so wt remove, wt merge, and wt step prune removed it without --force. Safety checks now always count untracked files, and auto-staging warnings list every file they stage. (#4111, thanks @Duang777)

• wt remove and wt merge check the right worktree under an inherited GIT_DIR: run from a !wt git alias or a git hook, which pass GIT_DIR down, wt remove could delete a dirty worktree without --force, and wt merge could refuse a clean merge. Both now check the worktree they act on. (#4082, thanks @Duang777)

• wt merge no longer deletes a worktree locked with git worktree lock: the merge completes and prints Worktree preserved (locked). Every Worktrunk removal refuses a locked worktree, even with --force; run git worktree unlock <path> first. (#4073, thanks @Duang777)

• wt config update no longer overwrites a config edited while its prompt is open: it wrote the pre-prompt snapshot over the newer file and reported success. It now fails with the path and leaves the newer file; re-running previews the current contents. (#4127, thanks @zach-hammad-vs for reporting)

• wt step prune no longer deletes a branch created minutes ago from an older commit: --min-age aged a branch without a worktree by its commit's date, so a new branch off a day-old commit was pruned on the next run. Age now comes from the branch's oldest reflog entry. (#4077)

• A comment or blank line above an inline config section no longer breaks the config: a save or migration that rewrote commit = { … } as [commit] put that line inside the brackets. wt switch, wt merge, wt remove, and several wt step commands then failed with Failed to load config; wt list warned and ran without the config. Saves also d

Release Notes

Improved

• wt list sizes and aligns its columns to the terminal width: one long branch name no longer sizes the Branch column for every row — it caps at 32 characters and elides, so a narrow terminal keeps its other columns instead of degenerating into a branch list. Remote⇅ stops holding blank space open in a repo with no remote, and alignment now follows the value type. --format=json still carries the whole name. (#3998)

• wt list names what it hid and marks detached worktrees: the summary reads hidden: Path, Commit instead of counting columns, a detached worktree shows ⊘ rather than borrowing ⚑, and a prunable row leaves its cells blank instead of showing loading dots that never resolve. (#3998)

• wt list --format=json gains a marker field and stops reporting detached twice: the branch marker set by wt config state marker is now readable without parsing it out of symbols, and state no longer reports a detached worktree as branch_worktree_mismatch — the sibling detached boolean carries it. (#3998)

• wt list --format=json now defaults to schema 2: callers get the envelope with repository metadata and orthogonal per-item facts without configuring [list] json-schema. wt list statusline --format=json follows the same key. Set json-schema = 1 to retain the original bare-array format. (Breaking.) (#4038)

• wt config show fails on a broken config: it exits 1 on an unreadable or invalid config, an invalid [list] columns, or an invalid approvals.toml. Unknown keys and deprecations stay warnings and still exit 0. A new APPROVALS section counts project commands awaiting approval. (Breaking: it always exited 0 before.) (#3999)

• Config migration output names its destination: wt config update --output <path> writes the migration artifact to that file instead of applying it in place, and --output=- writes it to stdout. Output mode includes project config when run from a linked worktree. (Breaking: --print was removed.) (#4021)

• Pi joins the agent integrations: wt config plugins pi install writes an activity hook to ~/.omp/agent/hooks/pre/worktrunk.ts, so Pi sessions show 🤖/💬 markers in wt list like Claude Code, Codex, OpenCode, and Gemini. $PI_CONFIG_DIR, $PI_CODING_AGENT_DIR, and named $OMP_PROFILE/$PI_PROFILE profiles are honored. Docs (#3594, thanks @adity982, and @ortonomy for the request)

• wt config plugins codex install installs the plugin too: it previously registered the marketplace and left you to run /plugins in Codex yourself. Uninstall follows for both Codex and Claude Code, removing the plugin and then the marketplace, so the two commands are inverses. (Breaking: Codex uninstall previously left an installed plugin alone; Claude uninstall now also removes the marketplace.) (#4019)

• wt step copy-ignored says whether it reflinked or copied: the summary now reads (reflinked, no extra disk), (full copy), or a partial count, so the same 29.5 GB line distinguishes a free copy from one that actually wrote the bytes. --format=json gains reflinked and written. (#4025)

• wt config update removes keys its destination cannot hold: migrating [select] or [commit-generation] drops keys the new section has no field for, reporting each one. Otherwise the key landed at a path the user never typed and warned on every command, with no way to clear it. ([#3994](https://github.com/max-si