About

Why I made Keleuo

I use Claude Code every day and I like it a lot. But at some point I noticed I had stopped really knowing what it was doing in my projects. Everything it does is right there on the screen. It just moves fast and says a lot, and after a few minutes I'm skimming. By the end of a session the work is done and I have a rough idea of how.

That bothers me. It's my code, and I want to know it.

Editors with an agent built in come at this from the other side. They're good, and I've used them. They're built around the file you have open, though, with the agent in a panel beside it. For a lot of my day the agent writes most of the code now, and I spend more time reading what it did than typing. I wanted a layout that matches that.

So Keleuo puts the agent first and keeps the code right next to it. I can follow what a session is doing and what it changed, and when something looks off I can open the file and fix it myself without leaving the window. The agent does more of the typing these days. I still want to be close enough to the work to know it well.

I built it for the way I work, and I'm not trying to win everyone over. If you've had the same feeling, that you don't quite know what your agent did today, it might suit you too.

What Keleuo is, and is not

Keleuo does not replace Claude Code and does not change how it works. Each session runs Claude Code's own terminal interface, as it is, in a real terminal. Keleuo reads along and adds layers on top:

A readable view of the session. Markdown rendered, tool calls folded into cards, real diffs, file links you can click, subagents as they run.
Questions you cannot miss. Permission prompts become buttons, and a session that needs you shows it in the list.
The project beside the agent. Files, an editor, terminals, the skills the agent will use, and the sessions that ran in this folder before.

The terminal is always one click away, and it is the same process: switching views starts and stops nothing. Keleuo never rewrites what the agent runs.

The Keleuo window: the session list, the project's files, and the agent's chat with tool calls and a diff.

Why native

I wanted it to feel like part of the machine, not a web page in a box. Keleuo is written in Rust on gpui, the GPU-accelerated framework behind the Zed editor. There is no browser engine inside, so it starts quickly and stays small.

How it is made

Keleuo is built with Claude Code, inside Keleuo. Most changes start as a conversation with Claude Code in the app, and that is also how the log gets written: each day, Claude writes up what changed and why, and I read it over before it goes up.

Open source

I made Keleuo for my own work and I am sharing it in case it helps yours. It is free and open source under the Apache 2.0 License. If it is useful to you, or something about it gets in your way, I would love to hear about it: issues, ideas and pull requests are all welcome on GitHub.

Keleuo is published by Wundur AI Learning, LLC. It works with Claude Code and is not affiliated with Anthropic.