GitLens, the popular Git visualization extension for Visual Studio Code, has released version 19.2 with significant improvements aimed at making the tool more accessible to international developers and more powerful for teams managing complex repositories. The update introduces experimental translations in Spanish and Chinese, alongside new features that let developers scope their Commit Graph to specific worktrees and resume past coding agent sessions.

Why Does Multi-Language Support Matter for Developers?

GitLens now automatically follows your VS Code display language settings, meaning developers no longer need to hunt for separate language preferences. If you install a Spanish or Chinese language pack in VS Code, GitLens switches over with it. The translations are AI-generated and have been reviewed for accuracy, though anything not yet translated falls back to English. Importantly, Git syntax, command references, file paths, and product names remain in English across all languages, so what you type and search for stays consistent everywhere.

This localization effort reflects a broader trend in developer tools recognizing that coding happens globally. By removing the friction of navigating an English-only interface, GitLens makes itself more welcoming to teams in non-English-speaking regions.

What Is Worktree Scoping and Why Should You Care?

One of the most significant additions in this release is the ability to scope the Commit Graph to a specific worktree. A worktree is essentially a separate working directory within a Git repository, allowing developers to work on multiple branches simultaneously without constantly switching contexts. With scoping, you can point the entire Commit Graph at one worktree, and all your actions run within that context.

When you scope to a worktree, several things happen automatically. The working changes for that worktree become the primary WIP (work in progress) row, branch markers and ahead/behind counts reflect that worktree's status, and every action you perform, whether committing, pulling, pushing, or switching branches, uses that worktree as the working directory. Because GitLens never re-walks the history when scoping or unscoping, the operation is instant and preserves your scroll position, selection, search filters, and other view preferences.

How to Manage Your Commit Graph Layout and Worktrees

• Scope to a Worktree: You can scope from worktree rows in the sidebar, by double-clicking a WIP row or overview bar pill, from WIP row context menus, or using the Focus in Commit Graph commands. A scoped graph tints its title bar and displays the worktree's branch name in a pill for easy identification.
• Save Your Layout as Default: Arrange columns, sizing, grouping, and panels how you prefer, then use the Save as Default Layout action in the column header or settings gear menus. This layout becomes the starting point for all new workspaces, saving you time on repetitive configuration.
• Customize Keyboard Shortcuts: The new gitlens.graph.shortcuts.overrides setting lets you rebind or disable the graph's modifier-key shortcuts by ID, or turn them all off entirely with gitlens.graph.shortcuts.enabled if you prefer to use your own keybindings.
• Run Tasks in Worktrees: Worktree WIP rows now include a Run Default Task button that executes your chosen default VS Code task in that worktree with a single click, eliminating the need to manually switch contexts before running build or test commands.

The scoping feature also introduces independence between scope and focus. Focus narrows the visible rows to a branch's history, while scope points the graph at a worktree's perspective. You can scope without focusing, meaning the graph still shows every commit unless you explicitly focus a branch too. Two settings control how they interact: gitlens.graph.scopeBehavior determines whether scoping also focuses the worktree's branch, and gitlens.graph.doubleClickWorktreeAction controls whether double-clicking a worktree scopes or just focuses it.

What Else Changed in GitLens 19.2?

Beyond localization and worktree improvements, GitLens added several quality-of-life enhancements. You can now resume past agent sessions from Codex, OpenCode, and GitHub Copilot CLI, with every resume action clearly indicating where the session will open, whether in a terminal or within the agent's own extension. The new gitlens.agents.resumeTarget setting lets you choose which destination Enter uses in the Resume Agent Session picker.

The Agents sidebar panel now provides clearer feedback when empty, explaining why instead of showing a generic "No items" message, and connecting agents is simpler with a connect action named for your default agent that opens GitLens Settings and installs that agent's hooks immediately. Additionally, a Generate Changelog action now works on multi-selected commits in the Commit Graph, even when the selection isn't contiguous, and working changes next steps now offer Force Push alongside Pull when a branch has diverged from its upstream.

The Home view has been retired since the Commit Graph now covers and expands on everything it provided. Onboarding has been consolidated into the Welcome view, and a new Send Feedback dialog puts feature requests and bug reports just one click away, making it easier for users to contribute to the tool's development.

For repositories where loading commit file details has been slow, the Commits and other history views now load them on demand automatically, removing the need to manually find and enable this setting yourself. These incremental improvements reflect GitLens' focus on reducing friction in the developer workflow, whether you're working solo or as part of a distributed team managing multiple branches and worktrees simultaneously.