GitKraken Desktop
GitLens for IDEs 
Kepler
GitKraken MCP
GitKraken CLI
GitKraken Insights
Git Integration for Jira
Dev Team Automations
AI & Security Controls
Supercharge Your Dev Team 
Secure Your Dev Team 
Project Kepler
Mission Control for Agent-driven Development
Claude in one terminal, Cursor in another, a Copilot PR waiting on review. They’re all working different corners of the same project. Kepler is where they meet: every agent on every task across every repo, with worktrees, branches, and merges handled for you.
Please use the email address tied to your GitKraken account.
The Agents Are Fast,
The Wrangling Isn't.
Branches collide across your repos
Worktrees pile up across every repo
No tool shows how your branches relate
Coordination becomes the job
Built around how you work with agents
One surface. Every agent.
Kick off, track, and resume agent sessions in one place. See what every active agent is doing, what it touched, and where its work stands. The UI auto-focuses on whatever thread you are in.
Related work, one task.
A database migration, an API change, and a front-end update are one effort. They shouldn’t live as three branches you re-stitch every context switch. In Kepler, related agent sessions belong to one task.
Worktrees, handled.
More agents means more worktrees, more branches, more state to track by hand. Kepler creates them, shows their state, flags branches about to collide, and cleans up the debris agents leave behind.
Plugs Into The Stack You Already Use
Kepler rides GitKraken’s git-native layer, so it speaks GitHub, GitLab, Bitbucket, and Azure DevOps the way your CLI does. Jira for tasks. Claude Code and Codex at launch, with Copilot and Gemini following.
Direct The Agents.
Drive The Work.
Waitlist members get first access, and a direct line to the product team.
Kepler Faqs
Kepler is GitKraken’s agentic development environment (ADE), which means it helps you kickoff coding agent sessions across multiple repos.
It gives developers full clarity and control to scale their use of parallel agents, across planning work, writing code, and reviewing what ships. You start from your existing backlog or PR queue, run agents across multiple repos, and see every session from one surface.
An ADE (Agentic Development Environment) is the workspace built for a developer whose primary job is no longer writing code but directing AI agents that write it. Where an IDE was built for one developer typing code, an ADE is built for one developer running multiple agents in parallel. Kepler is GitKraken’s ADE.
GitKraken Desktop is built for one developer, one agent, one repo at a time. Kepler is built for developers scaling parallel agents across multiple repos simultaneously. If you are already using GitKraken Desktop and managing several agents, Kepler is the next step. GitKraken Desktop remains the right tool for focused, single-repo work.
Kepler is agent-agnostic, and it currently integrates with v
Connect the agent you are already using and Kepler manages the sessions, visibility, and review around it. See the [integrations page] for the current list of supported agents.
A Task is the container that holds your work across repos. You start one from an issue in your tracker (like Jira, Linear, Trello, GitHub Issues, or GitLab Issues) or a PR in your queue. Kepler creates the worktrees, launches your agents, and keeps everything connected through shared context. A Task can span any number of repos.
Yes. Kepler connects to your issue tracker so you can select issues and have agents start on them directly. Connect to Jira, Linear, Trello, GitHub Issues, or GitLab Issues. You can also pick a pull request and have an agent handle the follow-on work. The entry points are the same ones you already use.
Yes. Kepler works with GitHub Enterprise and GitLab Self-Managed. Connecting to a self-hosted service requires a Personal Access Token with the appropriate permissions. See the Integrations documentation for setup instructions.
Add to Chrome
Add to Firefox
Add to Microsoft Edge