GitKraken Agent Management | Manage Your Agents, Your Way
Manage your agents, your way
GitKraken Agent Management is built into GitKraken Desktop, GitLens, and Kepler. Launch and monitor AI coding agents, and run work in parallel across your private repos, without leaving your normal tools.
Works with agents Across GitKraken
Kepler ADE
Direct agents across multiple repos and drive work from generated to merged in one surface.
GitKraken Desktop
Run and monitor agent sessions from a standalone app with a full visual commit graph and worktree management.
GitLens for IDEs
Manage agent sessions and compose commits without leaving VS Code.
GitKraken CLI
Interact with your repos, issues, and pull requests directly from the terminal.
Smoother Workflows With Seamless Integrations
GitKraken works natively with your repos, issues, IDEs, agents and more, so you can reduce context switching and focus on building.
One repo, multiple agents, one view
You’ve got three things going at once: a refactor in one worktree, a bug fix in another, a new feature in a third. Agent Sessions View keeps all three visible in one panel. You see status, changes, and PR state without jumping between terminals or losing your place in any of them.
One task, multiple repos
Kepler’s Tasks treat work across multiple repos as one unit. All your branches, agents, and PRs for that work are visible from one place. Branches stay current with auto-rebase. Everything drives toward merged code.
Frequently Asked Questions
What agents does GitKraken support?
GitKraken Desktop works with Claude Code, Codex CLI, Copilot CLI, Gemini CLI, and OpenCode. Kepler supports Claude Code, Codex, OpenCode, GitHub Copilot, and Cursor.
Do I need to already be using agents to get started?
No. If you’ve never run an agent before, GitKraken Desktop is a reasonable place to start. You can spin up one session, watch what happens, and review the output before anything gets committed.
What's the difference between GitKraken Desktop, GitLens, and Kepler?
GitKraken Desktop and GitLens both cover the single-repo story: multiple agents, one codebase, organized in one view. The difference is where you work. GitKraken Desktop is a standalone app; GitLens brings the same agent management capabilities into VS Code. Kepler is for a different problem: coordinating work across multiple repos as one Task.
Does GitKraken write code or send prompts to agents?
No. GitKraken Desktop launches external agent CLIs and shows you what they’re doing. It doesn’t write code, generate prompts, or send anything to the agent. The agent does the work. GitKraken helps you see it and manage it.
What does Commit Composer do?
Commit Composer takes the raw changes from an agent session and organizes them into logical, reviewable commits.