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.

Get into the Private Preview:

Please use the email address tied to your GitKraken account.

The Agents Are Fast,
The Wrangling Isn't.

Warning symbol

Branches collide across your repos

Worktree icon

Worktrees pile up across every repo

No visibility icon

No tool shows how your branches relate

Time management icon

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.

Github, OpenAI, Gitlab, Azure Devops, Bitbucket, Linear, Jira, OpenAI, Claude, Gemini, Trello and Codex
Github, OpenAI, Gitlab, Azure Devops, Bitbucket, Linear, Jira, OpenAI, Claude, Gemini, Trello and Codex

Direct The Agents.
Drive The Work.

Waitlist members get first access, and a direct line to the product team.

Request Early Access