chore(deps): update ⬆️ mise-packages - #964

v2.1.195

Compare Source

• Added CLAUDE_CODE_DISABLE_MOUSE_CLICKS to disable mouse click/drag/hover in fullscreen mode while keeping wheel scroll
• Fixed hook matchers with hyphenated identifiers (e.g. code-reviewer, mcp__brave-search) accidentally substring-matching — they now exact-match. Use mcp__brave-search__.* to match all tools from a hyphenated MCP server.
• Fixed voice dictation on macOS capturing silence in long-running sessions after the default input device changes
• Fixed voice dictation auto-submit never firing for languages written without spaces (Japanese, Chinese, Thai)
• Fixed external plugins enabled only by project .claude/settings.json not requiring explicit install consent on every loader path
• Fixed /plugin Enable/Disable not working when a plugin's plugin.json name differs from its marketplace entry name
• Fixed background jobs disappearing from claude agents or losing data when written by a newer Claude Code version
• Fixed reopening a crashed background task showing a blank screen for up to 5 seconds instead of its restart
• Fixed background agent daemons running unreachable when the control socket fails to start, blocking restarts
• Improved voice mode on Linux: now distinguishes "no microphone" from "SoX not installed" when SoX is present but no audio capture device exists
• Improved claude agents completed list to fill available vertical space; on short terminals the header compacts so live sessions stay visible
• Improved Remote session startup with a provisioning checklist while the container starts

v0.11.25

Compare Source

Released on 2026-06-26.

Security

This release updates our tar library, astral-tokio-tar, to v0.6.3, which includes over 20 changes that harden our tar handling against parser differentials. uv may reject source distributions with malformed or ambiguous content that were previously accepted.

See the upstream commits for a full list of changes.

Enhancements

• Add a full "lockfile" to tool receipts (#​18937)
• Allow scoped overrides to add dependencies (#​19974)
• Avoid writing redundant lockfile markers with tool.uv.environments (#​19933)
• Factor supported environments out of lockfile markers (#​19969)
• Recommend our own build backend in the build frontend (#​19994)
• Reject wheels with multiple .dist-info directories (#​19986)
• Simplify dependency markers under parent reachability (#​19971)
• Support scoped dependency exclusions (#​19977)
• Support scoped dependency overrides (#​19970)
• Explain why files are skipped in registry index parsing (#​19983)

Preview features

• Add uv workspace list --scripts (#​20009)
• Support centralised environments in uv venv (#​19912)
• Use locked ty versions in uv check (#​19884)
• Add centralized storage of project environments (#​18214)
• Verify lockfile hashes before reusing a cached ty in uv check (#​19995)
• Use locked dependency selection for uv check --script (#​19989)

Bug fixes

• Preserve standalone markers in workspace metadata (#​20011)
• Reject uv build if the cache dir is enclosed (#​19991)

v0.2.8

Compare Source

Features

#​453 #​466 Support disabling open browser

By default, ghtkn opens the browser automatically for the device flow if commands such as xdg-open exist on PATH.
You can disable this behavior by setting the GHTKN_OPEN_BROWSER environment variable or .open_browser.enable in a configuration file to false.

export GHTKN_OPEN_BROWSER=false

open_browser:
  enable: false

This is useful in environments where those commands exist on PATH but don't work.
For example, in WSL xdg-open exists but doesn't work. In that case, please open the browser yourself.

v0.31.1

Compare Source

Bug Fixes

• Fixed the React renderer so it picks the react-dom renderer instead of hardcoding renderer id 1, which prevented reading an empty tree on Next.js 16.3 Turbopack (#​1491)

Contributors

• @​gaojude

v0.62.0: 0.62.0

Compare Source

Release Notes

Improved

• Browse open PRs/MRs in the wt switch picker, with live CI: The picker now streams a live CI/review-status column per row — priming from the local cache, then fetching live (it previously showed only cached numbers with no network). A new --prs flag adds the repository's open PRs (GitHub) / MRs (GitLab) as rows alongside your worktrees, each with pr / comments / log preview tabs loaded from the forge in the background; selecting one fetches its branch and switches. Rows whose branch is already shown aren't duplicated, so --prs differs from plain wt switch only by the extra rows. Docs (#​3128, #​3169, #​3189, #​3252)

• main…± diff column shows by default in wt list: The main…± column (lines changed since the merge-base with the default branch) now renders in the default wt list and picker, served from a persistent cache rather than a history walk. --full now adds only the columns that reach off-machine — CI status and LLM branch summaries — and wt list --format=json populates main.diff for every item, not just under --full. (#​3236)

• [list] columns selects and orders the columns wt list shows: A new [list] columns user-config key (also settable via --config-set) takes an ordered array of column names — built-in (branch, status, ci, path, …) and [list.custom-columns] headers alike — and renders exactly those, in that order. Where v0.61.0's custom columns add columns, this selects and reorders the whole set; omit the key for the default layout. (WORKTRUNK__LIST__COLUMNS isn't supported yet and warns if set.) (#​3141)

• Picker PR preview shows full PR/MR detail: The pr tab now renders the PR/MR title, markdown description, author, draft state, comment count, bold branch name, and underlined URL for any row whose branch has an open PR — not just --prs rows — and the comments tab fetches the real thread. The title and description ride the CI fetch the picker already makes; the comment thread is fetched lazily in the background, once per row. (#​3167, #​3197, #​3223, #​3195, #​3231)

• Interactive picker runs on Windows: The wt switch picker was Unix-only because its preview-tab keys shelled out through a per-process state file cmd.exe lacks; tab state moved to an in-memory atomic with native skim callbacks, lifting the platform gate. (#​3217)

• Picker keyboard shortcuts: Alt-y copies the selected branch name, Alt-o opens the row's PR/MR in the browser, and Alt-r refreshes the list (picking up worktrees created or removed elsewhere). (Breaking: in the picker, remove moved from Alt-r to Alt-x) (#​3233)

• Picker uses the full terminal: List height scales with the terminal (a roughly even split with the preview, minimum 3 rows) instead of a fixed 12-row cap, the table lays out at full width so toggling the preview off with Alt-p reveals the freed columns with no reflow, and a scrollbar appears when the list overflows. (#​3205, #​3214, #​3198)

• Picker filters on more of each row: Typing a gutter sigil filters by row kind (+ for linked worktrees, @ for the current one), the fuzzy matcher ranks on the distinguishing path segment rather than the shared parent prefix, and rows with a PR/MR also match on its number, title, and author. (#​3143, #​3208, #​3252)

• Picker visual polish: The legend recolored to dim-cyan and reordered so navigation leads, and preview loading placeholders moved to the dim-hint style (↳ transient, ○ settled, ▲ failed). (#​3237, #​3253)

• "Still waiting" status for slow commit-message generation: A configured commit.generation command captures stdout, so a slow or hung LLM previously showed nothing while wt step commit/squash waited. After a 2s delay worktrunk now shows a dim, in-place ○ Waiting for the commit message (Ns) status, escalating at 10s to reveal the exact shell-escaped invocation in a gutter beneath it; the block clears on completion, mirroring wt list's stall footer. (#​3178)

• "Still waiting" status extended to more slow commands: The same waiting status now covers three more foreground commands that were silent while a captured subprocess ran — the wt config show --full commit-generation self-test, the wt switch pr:/mr: host lookup, and the wt config show --full version check. The version check no longer caps its fetch at an aggressive 5s, instead showing the status while a slow-but-working request completes (with a generous ceiling so a non-interactive run can't hang). (#​3183)

• wt config state logs profile performance profiler: A new subcommand turns a -vv [wt-trace] capture (a path argument, - for stdin, or the default trace.log) into a performance profile: subprocess time by command shape, the slowest calls, parallelism and peak concurrency, redundant cache-miss re-runs, and — for wt list/picker captures — derived latencies and a collect timeline. --format=json emits the same data, and every -vv bug-report bundle now inlines a rendered profile. (#​3184, #​3186)

• WORKTRUNK_VERBOSE env var: WORKTRUNK_VERBOSE=0|1|2 mirrors -v/-vv, combined with any flag via max (the env sets a floor the flag can raise). Unlike the flags it's honored on the shell-completion path, which returns before flag parsing — so a slow tab-completion can be profiled for the first time. (#​3166)

• Aliases inherit the wrapped command's completion: An alias that forwards {{ args }} to a single wt command (co = "wt switch {{ args }}") now completes that command's arguments and flags — wt co <Tab> completes branches like wt switch <Tab> — instead of a generic stub. Bare dispatchers and multi-{{ args }} aliases keep the stub. (#​3172, thanks @​yzx9)

• wt step copy-ignored --require-include: A new --require-include flag makes the copy a no-op unless a .worktreeinclude file exists in the source worktree (matching Claude Code desktop, where that file is required), reporting why it skipped as a hint in text mode and a reason field in --format=json. (#​3196, thanks @​yzx9)

• wt step tether honors -C: The global -C <path> flag now sets the tethered command's working directory (wt step tether -C frontend -- npm run dev); teardown still watches the worktree root, so the command is reaped when the worktree is removed. (#​3207)

• Statusline rate-limit pace color grades by severity: The pace segment's color now deepens (dim → dim-yellow → yellow) with the projected throttling severity, so an early-window burst stays muted while a costly projected lockout stands out. The displayed pace number is unchanged. (#​3229)

Fixed

• Picker Alt-x removal updates the row in place: Removing a worktree no longer re-collects the whole list (a flicker that reset the cursor to the top): an unmerged worktree's row morphs into a branch-only row while the worktree is removed in the background, and a merged worktree's row drops with the cursor landing on the row that slid up. A removal that can't safely happen — the current or main worktree, or a dirty or locked one — is declined with the same diagnostic wt remove prints, rather than a dead keypress or a disruptive cd home. The post-removal cursor lands by row identity, so it stays correct even under an active filter. (#​3262, #​3199, #​3211, #​3225)

• Picker preview refreshes when its background fetch lands: A diff/log/PR-view fetch that completed after its triggering keystroke used to sit unshown until the next keypress; the pane now updates on its own when the fetch lands. (#​3247)

• Picker rows stay aligned while filtering: Typing a filter no longer slides the matched row left and drops its leading sigil, and Alt-l/Alt-h no longer scroll the list off its gutter. (#​3213, #​3226)

• fish completions no longer recurse to the call-stack limit: With worktrunk's fish lazy-load wrapper installed, completion could re-enter the wrapper and recurse until fish hit its call-stack limit. The package-manager registration now resolves the real binary via type -P instead of calling the bare wt, and the wrapper stub short-circuits in completion mode the way the bash and zsh wrappers already did. (#​3241, #​3250; fixes #​3240, thanks @​maciej-lech for reporting)

• wt switch changes directory under fish with zoxide.fish: The fish integration used a bare cd, which the kidonng/zoxide.fish plugin intercepts as a fuzzy query, so a switch reported success but failed with zoxide: no match found. The wrapper now uses builtin cd, bypassing any user cd override. (#​3160, fixes #​3159, thanks @​anon-legion for reporting)

• wt switch pr:N resolves Azure DevOps projects with encoded path segments: Azure returns decoded project names while git remotes store them URL-encoded, so a project like project with spaces failed to match. Path segments are now canonicalized before comparing remotes and building Azure URLs. (#​3204, fixes #​3203, thanks @​jonasherfort)

• Recommended Claude Code commit command preserves apiKeyHelper auth: The suggested [commit.generation] command for Claude Code used --setting-sources='', which dropped user settings and broke authentication for setups that get their key via apiKeyHelper. It now uses --safe-mode --setting-sources='user': the run stays hermetic (no hooks, plugins, MCP, skills, or CLAUDE.md) but loads user settings so apiKeyHelper works (requires Claude Code ≥ 2.1.169). Existing user configs are not rewritten. (#​3170)

• Claude Code paths honor CLAUDE_CONFIG_DIR: worktrunk hardcoded ~/.claude for every Claude Code path, so on a machine that relocates the config tree via CLAUDE_CONFIG_DIR, wt config show wrongly reported the plugin and statusline as not installed and install-statusline wrote to a stray file Claude Code never reads. All three call sites now resolve through CLAUDE_CONFIG_DIR, falling back to ~/.claude. (#​3215, thanks @​tftio)

• Deprecated config keys migrate in --config-set, env vars, and inline tables: Deprecated keys were rewritten to canonical form only in config files; passed any other way they fell through as unknown fields and were silently dropped. wt --config-set 'merge.no-ff=true', WORKTRUNK__MERGE__NO_FF=true, and the inline merge = { no-ff = true } form now all migrate and take effect. (#​3152, #​3158)

• wt config show can't hang on the zsh compinit probe: The interactive zsh -ic probe that checks whether compinit is configured could hang indefinitely on compinit's insecure-directories prompt; it now has a 2s kill-on-timeout, declining to warn on timeout. (#​3165)

• Empty branch-name arguments rejected at the parse boundary: An empty value (e.g. wt step diff --branch=) was accepted and produced a garbled downstream diagnostic; all branch-name arguments now reject empty or whitespace-only values at the CLI edge with a standard usage error. A real missing branch still gets its normal "no worktree" diagnostic. (#​3179)

Documentation

• wt list JSON and help-text accuracy: The wt list help text and web docs now note which --format=json objects (ci, summary) require --full, and the status-symbol reference tables name each JSON field by type — correcting a wrong "only the first matching symbol is shown" note and an unreachable worktree.state value. (#​3139, #​3220, #​3224)

Internal

• Richer -vv diagnostics: -vv now also writes a machine-readable trace.jsonl (one JSON object per event) alongside trace.log, segments subprocess.log into per-command blocks joined to the trace by a seq field, and lists each log path on its own line; worktrunk's own log sites moved to native tracing. (#​3232, #​3182, #​3163)

Install worktrunk 0.62.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/max-sixty/worktrunk/releases/download/v0.62.0/worktrunk-installer.sh | sh && wt config shell install

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/max-sixty/worktrunk/releases/download/v0.62.0/worktrunk-installer.ps1 | iex"; git-wt config shell install

Install prebuilt binaries via Homebrew

brew install worktrunk && wt config shell install

Download worktrunk 0.62.0

Install via Cargo

cargo install worktrunk && wt config shell install

Install via Winget (Windows)

winget install max-sixty.worktrunk && git-wt config shell install

Install via AUR (Arch Linux)

paru worktrunk-bin && wt config shell install

v3.9.1

Compare Source