Claude Code 2.1.119: Vim Visual Mode, Custom Themes, and GitLab PR Support

Claude Code versions 2.1.118 and 2.1.119 shipped on April 23-24 with a handful of useful additions. None of these are headline features, but they’re the kind of quality-of-life improvements that accumulate into a noticeably better daily experience.

Vim Visual Mode

The most visible change is full vim visual mode support. You can now use v to enter character visual mode and V to enter visual-line mode, with selection highlighting, operators, and visual feedback all working as expected. In normal mode, j and k now navigate history when you’re at the input boundary rather than doing nothing.

If you use vim keybindings in Claude Code, this rounds out the experience considerably. The previous vim support handled the basics but the absence of visual selection made it awkward for anything involving text manipulation.

Custom Themes

Version 2.1.119 adds a proper theming system. You can now create and switch between named custom themes using /theme, or edit JSON files directly in ~/.claude/themes/. The /config command also now persists settings to ~/.claude/settings.json, so your preferences survive sessions without manual configuration.

This pairs well with the /focus command from earlier builds, which toggles focus view separately from the transcript. The session-level customization story has been getting more complete across recent releases.

/usage Replaces /cost and /stats

The /cost and /stats commands have been merged into /usage. Both old commands still work as shortcuts that open the relevant tab within /usage, so nothing breaks if you’ve built muscle memory around the old commands. The unified view is cleaner for checking both token consumption and cost in the same place.

—from-pr Now Works With GitLab and Bitbucket

The --from-pr flag, which lets you load a pull request as context for a Claude Code session, now supports GitLab, Bitbucket, and GitHub Enterprise in addition to GitHub.com. This matters for teams not running on GitHub, who couldn’t use the feature at all before. Configuration is through the standard remote settings in your project config.

Hook Error Improvements

Hook errors in the transcript now include the first line of stderr automatically. Previously you had to run with --debug to see what a hook was outputting when it failed. The new behavior makes basic hook troubleshooting faster without changing your invocation.

The full changelog is at github.com/anthropics/claude-code/releases.

Sources: Claude Code Changelog, GitHub Releases, Releasebot