Kepler has picked up a lot over the last few releases. So much, in fact, that Gyo, GitKraken’s Director of Engineering, had to trim his list before walking us through it.

We sat down with Gyo and Jonathan, our Product Advocate, to go through the highlights. Gyo explained what shipped and why. Jonathan put the features to work live, building themes, cleaning up tasks, and forking a session from Claude to Codex. Here’s what we learned.

Make Kepler yours with themes

The UI has changed a lot over the past couple of versions. The team keeps iterating to make Kepler easier to use and better looking, and the biggest visible change is themes.

You can now customize Kepler’s colors however you like. The team has shipped a few themes already, and anyone can build their own and share it by opening a PR to the public themes repo. Gyo’s contribution is called Quiet, a softer palette if you want something easier on the eyes.

You don’t need to hand-edit a color file, either. Jonathan asked Kep (more on Kep below) for “a blue and white theme” and got one called Delft on the first try. On the call, he asked for a black and orange Halloween theme. A minute later Kepler had built and installed it, named Jack-o’-lantern, and even Kep’s icon picked up the new look.

Meet Kep, your in-app assistant

Kep is Kepler’s new assistant. Find it in the top right corner of the window, or press Cmd+L (Ctrl+L on Windows and Linux).

Kep runs on your default agent and model, just like a session, and it knows Kepler inside out. You can:

• Ask anything about how Kepler works
• Launch tasks without opening the task launcher
• Ask about settings, or have Kep change them for you

Jonathan put it to a real chore: he often finishes work and forgets to archive it. He asked Kep which tasks were ready to archive. Kep checked his workspace through the Kepler MCP and found 8 finished tasks. From there, archiving took one click, with options to delete the matching worktrees and branches too.

Sessions that talk to each other

Every session now includes what the team calls the coordinator. It lets a session create new tasks, check the status of other tasks, and interact with other sessions.

There’s some overlap with Kep, which can do more. But giving sessions this ability on their own opens up a lot. Gyo says the team is already experimenting with it internally and “doing crazy stuff.”

Fork a session and hand it off

Forking lets you branch a session into a new one. Right-click a session in the left panel and choose New session from this one. There are two big reasons to do it:

• Experiment without clutter. Keep the original session as is and explore a side question in parallel, without clogging its context.
• Switch agents or accounts mid-task. Hand the session from Claude to Codex, or to another account on the same agent. If you burn through your quota on one account, keep going on your second one.

Forking differs from starting a fresh session with the + button. A new session gets the shared task context, such as linked issues and task notes. A forked session gets that plus the full transcript of the conversation so far.

Features worth a second look

Some of the most useful features have been around for a few versions. Gyo called them out because they’re easy to overlook.

MCP management. Configure your MCP servers once in Kepler instead of fiddling with settings in every harness.

Multiple accounts per agent. Keep your personal and work Claude accounts side by side. Contractors can keep a separate account for each client. Pair it with forking to move work between accounts.

Worktree and branch cleanup. Worktrees pile up fast and eat disk space. A new tool in Settings shows what you have and lets you clean it up, no digging required.

A more usable Agent Graph. The Agent Graph got refinements too, including the ability to approve permission requests right from the graph. As Gyo put it, the graph is a much easier way to follow a session than reading the conversation. Click any file to see its diff and leave comments on specific lines. Those comments go to your agent, not to GitHub, so you can point at exactly what to change instead of describing it.

Coming soon: automations and custom groups

Gyo closed with two features in the works.

Automations are in internal testing now. They let Kepler start work for you when something happens, like an issue getting assigned to you or a PR landing in your review queue. Instead of hunting for work and spinning up sessions by hand, you set a trigger and choose the action or prompt Kepler should run. The team wants to fine-tune it before release.

Custom groups will let you organize tasks into your own groups on top of the existing status grouping. Group every task tied to one piece of work and stop scrolling through one long list. You’ll be able to turn it off if you don’t need it. Gyo called it a lifesaver, and Jonathan was just as eager: he went looking for it during the demo before remembering it hadn’t shipped yet.

Try it yourself

Update Kepler, press Cmd+L, and ask Kep to make you a theme. Then fork a session and see what a second agent does with the same context. To see everything that changed, open Help and choose Show release notes.

Built a theme you love? Share it with the community by opening a PR to the themes repo.