Docs
kelve.aiGitHub

Open anything

Ask your agent to show you something, in your own words, and it opens in kelve. You can open it yourself from the command line too.

Ask your agent

  • “Show me what you did in kelve.” Opens what your agent did since it last showed you: what isn’t committed, or the commits since then, as one change. It never shows you the same thing twice.
  • “Show me the src folder in kelve.” Opens a folder.
  • “Show me this repo in kelve.” Opens all of it.
  • “Show me docs/retries.md in kelve.” Opens one file, or a few.
  • “Show me what this branch does, in kelve.” Opens a branch against where it left main.

Your agent shows you its work by itself when it’s done. As its turn ends, if it changed files and hasn’t shown them since, it’s asked to show the work. It shows it if the work is finished and worth showing. It shows its branch since where it left its base, committed or not. Showing it again updates the same thing in kelve. A commit, push or pull request after that opens nothing more.

Your agent gives what it opens a title, and a line on what it is or what changed and why. The title is in kelve’s bar. The line is at the top of what it opened, after “Claude Code said”.

Each thing opens in a new browser tab, starting kelve if it isn’t running. A kelve tab you have open on something else, perhaps another agent’s work, stays where it is.

What opens

  • A change opens on its own page, plainly. It says what it changes and why, and what each part did before.
  • A folder or a repo opens on its own page: what it’s for, then its parts.
  • A file opens plainly: what it’s for, then each part.

Text opens the same way as code: notes, docs, a spec or a book chapter. Read plainly says how each page is put together.

In order

Anything with files in it opens with a way in. That’s a change, a folder or some files. The way in is the order to read it, in parts. It’s the In order tab, the first in the side. Only a file opened alone has none.

Finding the way in is your agent’s first job, before anything is read. While your agent finds it, In order says your agent is finding a way in. The way in starts with the whole, under What this change does, or What this is for anything else. Then come the files to read first, at most 40, each with a line on why to read it now. The rest follows in parts, each named in plain words, with why it comes next.

The order follows how the work fits together, not the alphabet:

  • First, what the work says about itself.
  • Then where it starts.
  • Then the path one thing takes through it.
  • Tests and docs come last.

Read that way, each file builds on the one before, so you understand it in one pass. What no one needs to read to understand it, such as images or settings, is left off. It’s still under Files.

Your agent reads only the way in, then stops, so you can start reading at once. Each part waits until you ask for it, with Read these, so you go only as far as you need. A file you open is read when you open it, wherever it is.

On a stepWhat it means
A quiet step, with an empty dialYour agent hasn’t read it yet
Your agent’s dial, fillingIt’s reading it now
A filled squareRead by your agent, ready for you
A hollow squareYou’ve read it

You’ve read a step once you’ve seen it plainly, as your agent wrote it. As code, you’ve read it once you’ve seen it with its marks done. Next, on the right, is where to go on. It’s the first step you haven’t read, and it moves on as you read. At the end of a file, the next step is a click away.

From the command line

kelve open .

Opens this folder. Give it a folder or a file. With nothing, it opens kelve itself.

kelve diff

Opens what you haven’t committed yet. kelve diff main opens this branch against where it left main. kelve diff 3f2a9c1 opens one commit.

An agent working in a Git worktree shows what it’s done so far with kelve worktree, run in the worktree.

Opened again

kelve keeps what’s read. Open something again, and only what changed since is read again. If files were added or taken out, the rest of the path is found again, so a new file has its place.

What’s open, and what’s paused

What you open last is what your agent reads. Things you opened before it are paused. Their reading waits until you open them again, then carries on where it was. They’re under Paused in your agent’s list.

Your agent reads what it opened on its own, so agents in several tabs each read their own. When nothing’s taking your agent’s list, Copy what to say gives you the words to have it read what that tab has open, by its number.