From c288492419bf8dadd74f6b1210e2b5e5c3050158 Mon Sep 17 00:00:00 2001 From: Roberto Vizcarra Date: Mon, 18 May 2026 09:22:30 -0700 Subject: [PATCH 1/3] Initial draft of AI Agents Initial draft of AI Agents --- gitlens/GL-Agents.md | 335 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 335 insertions(+) create mode 100644 gitlens/GL-Agents.md diff --git a/gitlens/GL-Agents.md b/gitlens/GL-Agents.md new file mode 100644 index 0000000..613ae62 --- /dev/null +++ b/gitlens/GL-Agents.md @@ -0,0 +1,335 @@ +--- + +title: AI Agents in Gitlens +description: Using AI Agents in Gitlens +taxonomy: + category: gitlens + +--- + +# Using AI Agents in GitLens + +GitLens 18 introduces integrated AI agent workflows directly inside your IDE. Instead of managing coding agents through scattered terminal tabs, external apps, or separate extensions, GitLens surfaces agent status, worktree context, and actionable Git workflows directly within the Commit Graph and Home View. + +With GitLens, you can: + +- Monitor active AI coding agents without leaving the IDE +- Track agent sessions tied to branches and worktrees +- Review AI-generated changes inside the Commit Graph +- Compose commits directly from agent-produced work +- Quickly identify sessions waiting for input +- Manage parallel worktrees and WIP changes visually + +GitLens 18 currently supports Claude Code integrations through GitLens-managed hooks. + +--- + +# What Are Agent Sessions? + +An agent session represents an active AI coding workflow associated with a repository, branch, or worktree. + +GitLens tracks these sessions and surfaces their status throughout the interface so you can monitor progress and act on changes without constantly switching between terminals, chat panels, or external applications. + +Agent sessions can appear in: + +- The Home View +- The Commit Graph overview cards +- The Commit Graph details panel +- The Agent Sessions sidebar panel + +Each session displays contextual Git information including: + +- Associated branch +- Worktree +- Working changes +- Agent state +- Ahead/behind indicators +- Actions requiring attention + +--- + +# Installing Claude Code Hooks + +GitLens integrates with Claude Code using hooks that provide real-time session visibility. + +## Install Claude Code Hooks + +You can install hooks from several locations in GitLens: + +- Home View banner +- Commit Graph header +- Agent Sessions sidebar banner +- Integrations menu + +To install hooks: + +1. Open the GitLens Home View or Commit Graph +2. Select the Claude Code integration prompt +3. Follow the setup instructions +4. Reload VS Code or your IDE if prompted + +Once installed, GitLens automatically detects Claude Code sessions and surfaces their state throughout the UI. + +## Uninstall Hooks + +To remove Claude Code hooks: + +1. Open the Command Palette +2. Run: + +```text +GitLens: Uninstall Claude Code Hooks +``` + +--- + +# Understanding Agent Status Pills + +GitLens surfaces agent activity through status pills shown throughout the interface. + +Status pills are color-coded and animated to help you quickly understand what requires attention. + +## Agent States + +### Running + +The agent is actively processing changes or generating code. + +Running sessions display subtle pulse animations. + +### Waiting for Input + +The agent requires developer input before continuing. + +Waiting sessions display attention-grabbing animations and are surfaced prominently in overview cards. + +### Idle + +The session is connected but not currently performing actions. + +### Completed + +The agent finished its current task and changes are ready for inspection or review. + +--- + +# Using the Agent Sessions Panel + +GitLens 18 adds a dedicated Agent Sessions panel available from: + +- The Home View +- The Commit Graph sidebar + +The Agent Sessions panel provides a centralized place to monitor all active sessions. + +## Features + +The panel includes: + +- Session status pills +- Branch and worktree associations +- Quick actions +- List and tree layouts +- Session grouping by workspace or worktree + +## Switch Between List and Tree Layouts + +Use the layout toggle in the Agent Sessions panel toolbar to switch between: + +- List layout +- Tree layout + +Tree layout is especially useful when working across multiple repositories or worktrees. + +--- + +# Reviewing Agent-Generated Code + +GitLens 18 turns the Commit Graph into a full review surface for AI-assisted workflows. + +From the Commit Graph details panel you can: + +- Inspect working changes +- Compare revisions +- Review AI-generated code +- Generate commits with Commit Composer +- Resolve conflicts +- Stage and unstage files + +## Open the Commit Graph Details Panel + +To open the details panel: + +1. Open the Commit Graph +2. Select a commit, branch, or WIP row +3. Toggle the details panel if it is hidden + +The panel can be docked: + +- On the right side of the Graph +- At the bottom of the Graph + +Hold `Alt` while toggling the panel to switch docking locations. + +--- + +# AI Code Review in the Graph + +GitLens 18 adds AI-powered review workflows directly inside the Commit Graph. + +## Start an AI Review + +1. Open the Commit Graph +2. Select a WIP row or commit +3. Open the details panel +4. Switch to Review mode + +GitLens generates: + +- Review summaries +- Suggested focus areas +- Severity indicators +- File-level context + +This helps you validate AI-generated changes before committing or opening a pull request. + +> AI Code Review requires GitLens Pro. + +--- + +# Compose Commits from Agent Changes + +Commit Composer is now integrated directly into the Commit Graph details panel. + +You can generate structured commits from working changes without leaving the Graph. + +## Compose a Commit + +1. Open the Commit Graph +2. Select a WIP row +3. Open the details panel +4. Switch to Compose mode +5. Review proposed commit groupings +6. Edit the generated commit message if needed +7. Commit the changes + +Compose mode supports: + +- Multi-diff previews +- Staged and unstaged files +- Untracked files +- AI-generated commit messages + +--- + +# Multi-Worktree Workflows + +GitLens 18 introduces multi-worktree WIP rows in the Commit Graph. + +Instead of only showing changes for the active worktree, the Graph now displays work-in-progress rows for every connected worktree. + +This makes it easier to: + +- Monitor parallel agent workflows +- Compare work across tasks +- Review uncommitted changes +- Resolve conflicts +- Compose commits from multiple worktrees + +Each WIP row updates live as files change. + +## WIP Scroll Markers + +The Commit Graph minimap now includes WIP scroll markers that highlight work-in-progress rows. + +You can: + +- Customize marker colors +- Enable or disable markers in settings + +--- + +# Focus Branch Mode + +Focus Branch mode helps reduce Graph noise when working on a specific branch or task. + +When enabled, the Commit Graph scopes itself to the branch you care about. + +## Enable Focus Branch Mode + +1. Open the Commit Graph +2. Open the scope menu in the Graph header +3. Select a branch to focus + +While focused: + +- The Graph follows the branch's first-parent history +- The minimap zooms to the relevant commit range +- Simplify Merge History is automatically applied +- Visual indicators show that the Graph is scoped + +--- + +# Pin a Branch to the Left Side of the Graph + +GitLens 18 allows you to pin an important branch to the leftmost column of the Commit Graph. + +This helps keep long-lived reference branches like `main` or `develop` visible while navigating complex histories. + +## Pin a Branch + +1. Right-click a branch row +2. Select: + +```text +Pin Branch +``` + +Pinned branches remain visible across Graph sessions. + +--- + +# Conflict Resolution Workflows + +Conflict resolution workflows now extend directly into the Commit Graph. + +You can resolve merge conflicts from: + +- Commit Graph WIP rows +- The Interactive Rebase editor + +Conflict states are surfaced inline inside the details panel. + +--- + +# Open the Commit Graph in a New Window + +GitLens 18 adds support for opening the Commit Graph in a detached window. + +This is especially useful for: + +- Multi-monitor setups +- Large repositories +- Persistent review workflows +- Parallel agent workflows + +## Open in a New Window + +From the Commit Graph menu, select: + +```text +Open in New Window +``` + +--- + +# Related Features + +GitLens agent workflows work especially well alongside: + +- Commit Composer +- AI Code Review +- Worktrees +- Launchpad +- Interactive Rebase +- GitKraken MCP integrations From 7545df55529062edb1ed04c097fe350447bbf87c Mon Sep 17 00:00:00 2001 From: Roberto Vizcarra <#> Date: Mon, 18 May 2026 09:38:54 -0700 Subject: [PATCH 2/3] =?UTF-8?q?docs(phase5):=20apply=20Google=20Technical?= =?UTF-8?q?=20Writing=20improvements=20to=20GL-Agents.md=20=E2=80=94=20202?= =?UTF-8?q?60518T1200?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- gitlens/GL-Agents.md | 194 ++++++++++++++++--------------------------- 1 file changed, 70 insertions(+), 124 deletions(-) diff --git a/gitlens/GL-Agents.md b/gitlens/GL-Agents.md index 613ae62..be1db09 100644 --- a/gitlens/GL-Agents.md +++ b/gitlens/GL-Agents.md @@ -7,7 +7,9 @@ taxonomy: --- -# Using AI Agents in GitLens +Last updated: May 2026 + +## Using AI Agents in GitLens GitLens 18 introduces integrated AI agent workflows directly inside your IDE. Instead of managing coding agents through scattered terminal tabs, external apps, or separate extensions, GitLens surfaces agent status, worktree context, and actionable Git workflows directly within the Commit Graph and Home View. @@ -24,13 +26,13 @@ GitLens 18 currently supports Claude Code integrations through GitLens-managed h --- -# What Are Agent Sessions? +## Understand Agent Sessions An agent session represents an active AI coding workflow associated with a repository, branch, or worktree. -GitLens tracks these sessions and surfaces their status throughout the interface so you can monitor progress and act on changes without constantly switching between terminals, chat panels, or external applications. +GitLens tracks these sessions and surfaces their status throughout the interface so you can monitor progress and act on changes without switching between terminals, chat panels, or external applications. -Agent sessions can appear in: +Agent sessions appear in: - The Home View - The Commit Graph overview cards @@ -48,12 +50,10 @@ Each session displays contextual Git information including: --- -# Installing Claude Code Hooks +## Install Claude Code Hooks GitLens integrates with Claude Code using hooks that provide real-time session visibility. -## Install Claude Code Hooks - You can install hooks from several locations in GitLens: - Home View banner @@ -61,20 +61,18 @@ You can install hooks from several locations in GitLens: - Agent Sessions sidebar banner - Integrations menu -To install hooks: +### Install Hooks -1. Open the GitLens Home View or Commit Graph -2. Select the Claude Code integration prompt -3. Follow the setup instructions -4. Reload VS Code or your IDE if prompted +1. Open the GitLens Home View or Commit Graph. +2. Select the Claude Code integration prompt. +3. Follow the setup instructions. +4. Reload VS Code or your IDE if prompted. Once installed, GitLens automatically detects Claude Code sessions and surfaces their state throughout the UI. -## Uninstall Hooks +### Uninstall Hooks -To remove Claude Code hooks: - -1. Open the Command Palette +1. Open the Command Palette. 2. Run: ```text @@ -83,25 +81,17 @@ GitLens: Uninstall Claude Code Hooks --- -# Understanding Agent Status Pills - -GitLens surfaces agent activity through status pills shown throughout the interface. - -Status pills are color-coded and animated to help you quickly understand what requires attention. +## Understand Agent Status Pills -## Agent States +GitLens surfaces agent activity through status pills shown throughout the interface. Status pills are color-coded and animated to help you quickly identify what requires attention. ### Running -The agent is actively processing changes or generating code. - -Running sessions display subtle pulse animations. +The agent is actively processing changes or generating code. Running sessions display subtle pulse animations. ### Waiting for Input -The agent requires developer input before continuing. - -Waiting sessions display attention-grabbing animations and are surfaced prominently in overview cards. +The agent requires your input before continuing. Waiting sessions display attention-grabbing animations and appear prominently in overview cards. ### Idle @@ -109,20 +99,15 @@ The session is connected but not currently performing actions. ### Completed -The agent finished its current task and changes are ready for inspection or review. +The agent finished its current task. Changes are ready for inspection or review. --- -# Using the Agent Sessions Panel +## Use the Agent Sessions Panel -GitLens 18 adds a dedicated Agent Sessions panel available from: - -- The Home View -- The Commit Graph sidebar +GitLens 18 adds a dedicated Agent Sessions panel available from the Home View and the Commit Graph sidebar. The panel provides a centralized place to monitor all active sessions. -The Agent Sessions panel provides a centralized place to monitor all active sessions. - -## Features +### Panel Features The panel includes: @@ -132,18 +117,13 @@ The panel includes: - List and tree layouts - Session grouping by workspace or worktree -## Switch Between List and Tree Layouts - -Use the layout toggle in the Agent Sessions panel toolbar to switch between: - -- List layout -- Tree layout +### Switch Between List and Tree Layouts -Tree layout is especially useful when working across multiple repositories or worktrees. +Use the layout toggle in the Agent Sessions panel toolbar to switch between list and tree layouts. Tree layout is especially useful when working across multiple repositories or worktrees. --- -# Reviewing Agent-Generated Code +## Review Agent-Generated Code GitLens 18 turns the Commit Graph into a full review surface for AI-assisted workflows. @@ -156,33 +136,26 @@ From the Commit Graph details panel you can: - Resolve conflicts - Stage and unstage files -## Open the Commit Graph Details Panel +### Open the Commit Graph Details Panel -To open the details panel: +1. Open the Commit Graph. +2. Select a commit, branch, or WIP row. +3. Toggle the details panel if it is hidden. -1. Open the Commit Graph -2. Select a commit, branch, or WIP row -3. Toggle the details panel if it is hidden - -The panel can be docked: - -- On the right side of the Graph -- At the bottom of the Graph - -Hold `Alt` while toggling the panel to switch docking locations. +The panel can be docked on the right side or at the bottom of the Commit Graph. Hold `Alt` while toggling the panel to switch docking locations. --- -# AI Code Review in the Graph +## Run AI Code Review in the Commit Graph GitLens 18 adds AI-powered review workflows directly inside the Commit Graph. -## Start an AI Review +### Start an AI Code Review -1. Open the Commit Graph -2. Select a WIP row or commit -3. Open the details panel -4. Switch to Review mode +1. Open the Commit Graph. +2. Select a WIP row or commit. +3. Open the details panel. +4. Switch to Review mode. GitLens generates: @@ -197,21 +170,19 @@ This helps you validate AI-generated changes before committing or opening a pull --- -# Compose Commits from Agent Changes - -Commit Composer is now integrated directly into the Commit Graph details panel. +## Compose Commits from Agent Changes -You can generate structured commits from working changes without leaving the Graph. +Commit Composer is integrated directly into the Commit Graph details panel. You can generate structured commits from working changes without leaving the Commit Graph. -## Compose a Commit +### Compose a Commit -1. Open the Commit Graph -2. Select a WIP row -3. Open the details panel -4. Switch to Compose mode -5. Review proposed commit groupings -6. Edit the generated commit message if needed -7. Commit the changes +1. Open the Commit Graph. +2. Select a WIP row. +3. Open the details panel. +4. Switch to Compose mode. +5. Review proposed commit groupings. +6. Edit the generated commit message if needed. +7. Commit the changes. Compose mode supports: @@ -222,11 +193,9 @@ Compose mode supports: --- -# Multi-Worktree Workflows +## Manage Multi-Worktree Workflows -GitLens 18 introduces multi-worktree WIP rows in the Commit Graph. - -Instead of only showing changes for the active worktree, the Graph now displays work-in-progress rows for every connected worktree. +GitLens 18 introduces multi-worktree WIP rows in the Commit Graph. Instead of showing changes only for the active worktree, the Commit Graph displays work-in-progress rows for every connected worktree. This makes it easier to: @@ -238,82 +207,59 @@ This makes it easier to: Each WIP row updates live as files change. -## WIP Scroll Markers - -The Commit Graph minimap now includes WIP scroll markers that highlight work-in-progress rows. - -You can: +### Use WIP Scroll Markers -- Customize marker colors -- Enable or disable markers in settings +The Commit Graph minimap includes WIP scroll markers that highlight work-in-progress rows. You can customize marker colors or enable and disable markers in settings. --- -# Focus Branch Mode +## Use Focus Branch Mode -Focus Branch mode helps reduce Graph noise when working on a specific branch or task. +Focus Branch mode reduces Commit Graph noise when working on a specific branch or task. When enabled, the Commit Graph scopes itself to the branch you select. -When enabled, the Commit Graph scopes itself to the branch you care about. +### Enable Focus Branch Mode -## Enable Focus Branch Mode - -1. Open the Commit Graph -2. Open the scope menu in the Graph header -3. Select a branch to focus +1. Open the Commit Graph. +2. Open the scope menu in the Commit Graph header. +3. Select a branch to focus. While focused: -- The Graph follows the branch's first-parent history +- The Commit Graph follows the branch's first-parent history - The minimap zooms to the relevant commit range -- Simplify Merge History is automatically applied -- Visual indicators show that the Graph is scoped +- Simplify Merge History applies automatically +- Visual indicators show that the Commit Graph is scoped --- -# Pin a Branch to the Left Side of the Graph - -GitLens 18 allows you to pin an important branch to the leftmost column of the Commit Graph. +## Pin a Branch in the Commit Graph -This helps keep long-lived reference branches like `main` or `develop` visible while navigating complex histories. +GitLens 18 allows you to pin an important branch to the leftmost column of the Commit Graph. This keeps long-lived reference branches like `main` or `develop` visible while you navigate complex histories. -## Pin a Branch +### Pin a Branch -1. Right-click a branch row +1. Right-click a branch row. 2. Select: ```text Pin Branch ``` -Pinned branches remain visible across Graph sessions. +Pinned branches remain visible across Commit Graph sessions. --- -# Conflict Resolution Workflows - -Conflict resolution workflows now extend directly into the Commit Graph. - -You can resolve merge conflicts from: +## Resolve Conflicts in the Commit Graph -- Commit Graph WIP rows -- The Interactive Rebase editor - -Conflict states are surfaced inline inside the details panel. +Conflict resolution workflows extend directly into the Commit Graph. You can resolve merge conflicts from Commit Graph WIP rows or the Interactive Rebase editor. Conflict states appear inline inside the details panel. --- -# Open the Commit Graph in a New Window - -GitLens 18 adds support for opening the Commit Graph in a detached window. - -This is especially useful for: +## Open the Commit Graph in a New Window -- Multi-monitor setups -- Large repositories -- Persistent review workflows -- Parallel agent workflows +GitLens 18 adds support for opening the Commit Graph in a detached window. This is especially useful for multi-monitor setups, large repositories, persistent review workflows, and parallel agent workflows. -## Open in a New Window +### Open in a New Window From the Commit Graph menu, select: @@ -323,7 +269,7 @@ Open in New Window --- -# Related Features +## Related Features GitLens agent workflows work especially well alongside: From 751206616e629dd4e56b72a20c5e43412543d14a Mon Sep 17 00:00:00 2001 From: Roberto Vizcarra <#> Date: Mon, 18 May 2026 09:59:08 -0700 Subject: [PATCH 3/3] =?UTF-8?q?docs:=20add=20related=20feature=20links=20t?= =?UTF-8?q?o=20GL-Agents.md;=20mark=20AI=20Code=20Review=20as=20coming=20s?= =?UTF-8?q?oon=20=E2=80=94=2020260518T1200?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- gitlens/GL-Agents.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/gitlens/GL-Agents.md b/gitlens/GL-Agents.md index be1db09..fd8d8c5 100644 --- a/gitlens/GL-Agents.md +++ b/gitlens/GL-Agents.md @@ -273,9 +273,9 @@ Open in New Window GitLens agent workflows work especially well alongside: -- Commit Composer -- AI Code Review -- Worktrees -- Launchpad -- Interactive Rebase -- GitKraken MCP integrations +- [Commit Composer](/gitlens/gitlens-features/#commit-composer-view-pro) +- AI Code Review *(Coming Soon)* +- [Worktrees](/gitlens/gl-worktrees/) +- [Launchpad](/gitlens/gl-launchpad/) +- [Interactive Rebase](/gitlens/gitlens-features/#interactive-rebase-editor) +- [GitKraken MCP integrations](https://help.gitkraken.com/mcp/mcp-tools-reference/)