Agents made code cheap.
Your attention isn't.

Kepler runs each task in its own worktree with the agent you choose, takes it to a pull request, and brings you only what needs you.

A desktop app for macOS, Windows and Linux.

Hi, I'm Kep.

Claude Code needs you on kepler/auth-overhaul.

Illustration of the Kepler Dashboard. A top bar with New task and Ask Kepler, the Todo and Tasks views, and a toolbar with search, Group by Inbox and the preview pane. The list is grouped into Needs attention, Running, Recent and Not started, and each task under Needs attention names its reason: Approval needed, CI failing, Changes requested. The first, Auth overhaul, is open in the preview pane, where Claude Code asks to start Codex on the task Revoke tokens on logout in Chat mode, with Approve and Deny. Over time the request is approved and Revoke tokens on logout moves from Not started to Running, a pull request moves to Done, a new task joins, and another task asks for your attention.

With the agent you choose, per task

  • Claude Code
  • Codex
  • GitHub Copilot
  • Cursor
  • Auggie
  • OpenCode
  • Grok
  • Pi
  • Antigravity

What Kepler handles so you don't.

Five things that used to pull you back to a terminal, each with a button. Go on, press them.

  1. 01

    Agents that start agents, kept in view

    An agent can create tasks and sessions of its own, pick the agent for each, message the ones it started and read what they report back. Before it starts a session, Kepler asks you, and every task it creates lands on the Dashboard like any other.

    Kepler is growing into the place you run the whole fleet from.

    Three agents on one task.

    Auth overhaul Claude Code

    Split the auth work into refresh rotation, revoke on logout and a test matrix. Run them in parallel and report back.

    Three pieces: two sub-agents of my own, and a Codex session for the revoke work. I will read its report when it lands.

    Approved: Start Codex on Revoke tokens on logout in Chat mode
    Subagent Refresh token rotation Running Activity: rewriting refresh() to rotate on every use
    Subagent Auth test matrix Completed Result: 14 cases across expired, revoked and rotated tokens
    Claude Code hasn't read 1 report from other agents

    Revoke on logout reports done. My sub-agents are finishing; one pull request per branch as each lands.

    Related tasks
    • ParentAuth overhaulClaude Code
    • Sub-taskRevoke tokens on logoutCodex

    A demo. A Subagent card is the agent's own helper inside its session; a sub-task is a separate task whose session the agent started through Kepler. Each session has an inbox of reports from the sessions it works with.

  2. 02

    The approval, where you are

    Before an agent syncs a branch, starts a session or rewrites a note, Kepler pins the request above the session's composer and runs it only once you approve. The Dashboard row reads Approval needed, a desktop notification arrives, and on macOS you can approve from it.

    Codex is waiting on you.

    Approval request from Codex Fix token refresh on expired sessions

    Sync kepler/fix-auth with its target

    Operation
    Rebase onto main
    Repository
    relay-web
    Behind main
    4 commits

    Always approve is not offered for actions that can lose work.

    Approved. Codex is rebasing kepler/fix-auth onto main, and the task is back to Running. Denied. The rebase does not run.

    A demo. In Kepler this card sits above the session's composer, the row reads Approval needed under Needs attention, and a notification titled Approval needed arrives.

  3. 03

    The conflict, resolved with its reasons

    When an update would conflict, let AI rebase or merge. Review each file's versions, with the reason for every resolution, before you apply.

    AI conflict resolution needs a paid GitKraken plan.

    Three files to settle.

    Sync kepler/fix-auth with conflicts Rebase onto main
    1. src/auth/refresh.ts AI Kept both: main's renamed helper and this branch's retry loop.
    2. src/auth/session.test.ts Auto Changes did not overlap.
    3. package.json Theirs Check: package.json, low confidence. Main's version bump kept.
    Ready to apply. Needs review: 1 file

    A demo. The sync panel lists every file with how it was resolved, and the versions behind each one are a click away.

  4. 04

    The usage limit, waited out

    When an account reaches its usage limit the session pauses, then resumes and sends its queued prompt on its own once the limit resets. Or continue as another account.

    More than one account per agent depends on your GitKraken plan.

    Claude Code is out of room until 11:40.

    Retry failed webhook deliveries Claude Code
    Running Resumed on its own
    5h
    3% used Resets 16:40
    7d
    62% used On pace
    Sent Now add the dead-letter table and a retry test for it. Sent at 11:40, when the limit reset.
    Continue as another account 11:40

    A demo. Usage bars show your pace against the time elapsed, and turn amber above 75% and red above 90%.

  5. 05

    The review comment, answered

    Comment on any line of a diff and send it to the agent now, or queue it for its next turn. Agents reply in a thread and can resolve it. A comment stays with the code as it changes, or is marked Outdated when its lines are gone.

    Codex is listening.

    src/auth/refresh.ts kepler/fix-auth
    1. 38 const token = await store.read(sessionId);
    2. 39- if (token.expiresAt > now) return token;
    3. 39+ if (token.expiresAt > now && !token.revoked) return token;
    4. 40+ for (let i = 0; i < 3; i++) {
    5. 41+ const fresh = await refresh(token);
    You Use the existing withRetry helper here instead of a new loop.
    Codex Switched to withRetry() and dropped the loop. The new test still passes.

    A demo. A comments list shows every comment of a task by file or status.

Open up to 16 tasks side by side in a grid, and the tray icon shows the most urgent state: needs you, failed, unread or working.

Every task, from issue to pull request.

Each task gets a worktree of its own, can span several repositories, and is finished once every one of its pull requests is merged. Nothing shares a working copy, so six tasks run as calmly as one.

Start from an issue or pull request on
  • GitHub
  • GitLab
  • Jira
  • Linear
  • Azure DevOps
  • Bitbucket
  • Asana

Walk away. The work keeps going.

Kep is asleep. The agents aren't.

Sessions outlive your attention, and Kepler's own restarts.

  • Through an update

    Agents and terminal sessions run under a supervisor. Shell tabs keep running through an app update and come back after a restart.

  • On hold until CI passes

    Put a task on hold until its pull request's CI passes, a review arrives or it merges. The task wakes by itself, even if that happened while Kepler was closed, and tells you why.

  • Even the ones you started yourself

    Kepler finds agent sessions you started in your own terminal. Preview the transcript, then continue it, fork it, or adopt it into a task.

  • From your phone, with Remote Access

    This machine's tasks and sessions open in your phone's browser through a secure GitKraken relay, so the one question that came up gets answered without a trip back to your desk. Turn it on, scan the QR code and sign in with your GitKraken account. Nothing to install, no VPN or port forwarding, and only you can connect.

    Remote Access is part of paid GitKraken plans.

From the team behind GitKraken and GitLens

Glad you're here.

Download Kepler

A desktop app for macOS, Windows and Linux. Pick your platform and architecture.

Apple silicon. Intel Macs use kepler-x64.dmg below.