GitLens Documentation

GitLens FAQ

Last updated: September 2026

Get answers to frequently asked questions about GitLens features, sign-in options, and GitKraken account integration.


What is GitLens Community vs GitLens Pro?

Learn about the differences between the two versions on the GitLens Community vs GitLens Pro page.


How Do I Sign In or Out of GitLens?

Sign In to GitLens

To sign in with your GitKraken account:

  • Click the GitLens icon in the sidebar.
  • Under GITKRAKEN ACCOUNT, select Sign In.
GitLens sidebar with sign-in option
Sign in from the GitLens sidebar

You can also sign in via the VS Code Command Palette:

  • Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P).
  • Type and select GitLens: Sign In to GitKraken....
VS Code Command Palette filtered to "GitLens: Sign" with the GitLens: Sign In to GitKraken command highlighted
Sign in using the command palette

Sign Out of GitLens

To sign out:

  • Click the GitLens icon in the sidebar to open the Home view.
  • Select the account chip (your plan name) at the top of the view, then select the Sign Out button in the popover.
The GitLens Home view with the account chip's popover open: the GitLens Pro plan header with its ENTERPRISE badge and the Synchronize Status, Manage Account and Sign Out icon buttons — Sign Out ringed — above the organization row and the Refer a friend link (the account's name, e-mail and avatar are blanked)
Sign out from the GitLens sidebar

Or use the VS Code Command Palette:

  • Open the Command Palette (Ctrl+Shift+P or Cmd+Shift+P).
  • Type and select GitLens: Sign Out of GitKraken.
VS Code Command Palette filtered to "GitLens: Sign" with the GitLens: Sign Out of GitKraken command highlighted
Sign out using the command palette

How do I enable debug logging?

You can enable debug logging by opening the Command Palette (ctrl+shift+p or command+shift+p) and running the command GitLens: Enable Debug (Trace) Logging.

VS Code Command Palette filtered to "GitLens: Debug Logging" with the GitLens: Enable Debug (Trace) Logging command highlighted

To view logs, open the Output Window (View > Output). The logs will be listed in the GitLens and GitLens (Git) channels. These channels can be toggled from the dropdown.


How can I export logs?

You can export logs using the actions in the overflow menu of the Output view.


Can GitLens or Visual Studio Code Work with a Proxy?

Yes. GitLens has no proxy setting of its own; it uses Visual Studio Code’s Http: Proxy settings (http.proxy and related settings). To open these settings, use the keyboard shortcut command/ctrl + ,. Then, search for http.proxy to see the related settings.

VS Code Settings editor searched for "http.proxy": the Http: Proxy settings — Proxy (empty), Proxy Authorization, Proxy Kerberos Service Principal, Proxy Strict SSL (checked) and Proxy Support — each with its description


Does GitLens Support Git Submodules?

Yes. GitLens provides basic Git submodule support, including automatic discovery and tracking of submodules in your workspace. Submodules are distinguished with their own icons in sidebar views, and diffs correctly handle submodule pointer changes. GitLens detects superproject paths and tracks submodule status alongside your main repository.


Can I Use My GitLens Paid License on More Than One Computer?

Yes. Your GitLens Pro license is tied to your email address, not a specific device. You can activate and use GitLens on multiple computers using the same account.

Have feedback about this article? Did we miss something? Let us know!
On this page