tourer

tourer gives you a guided tour of a folder you have never seen. A coding agent, Claude Code or Codex, reads the folder and plans the tour as a list of stops. Each stop explains one part of the code and links to the lines it talks about, which open in a pane next to the text.

The tour is shaped like a tree. The stops are the trunk: the order the guide thinks you should read things in, from what the folder is down to how its parts work. Each stop grows its own branch of questions. When something is unclear you ask right there, the answer stays with that stop, and you can keep following up until it makes sense. Then you go back to the trunk and carry on. Nothing ends up in one long chat you have to scroll back through.

tour
├─ 1  what tourer is and how it starts
│   ├─ why is there a separate daemon?
│   └─ where are tours saved?
├─ 2  the tour data model
│   └─ what does a revision count?
├─ 3  planning a tour
│   ├─ what if the planner stops early?
│   ├─ how are its lines parsed?
│   └─ ...
└─ ...

A question is sent along with the stop you are at, and with the lines you selected if you ask from the code pane. Every stop and answer suggests a few follow-ups, which you can ask with a number key.

What else it doesh2

The guide leaves short notes on single lines of code. Hover one, or put the code cursor on it, and you get a few sentences on why the line is there.

You can start asking while later stops are still being planned. If the guide learns that an earlier stop or answer was wrong, it fixes it, and marks what you haven’t seen yet with ✦.

Before a tour is planned you can give it instructions, like “start at main.rs and follow one request end to end”. The guide keeps to them when it answers, too.

Tours are saved together with the guide’s conversation, so you can close the terminal and pick up where you left off the next day.

Installh2

cargo install tourer

tourer doesn’t call a model itself. It runs the CLI of a coding agent you already use, read-only, in the folder you are touring. You need one of these on your PATH and logged in:

• Claude Code (claude)
• Codex (codex)

It runs on your agent subscription or API key like any other session, and your code goes to that agent’s provider just as it would if you used the agent directly.

Useh2

tourer path/to/folder

The start screen lets you continue the folder’s saved tour or plan a new one, and pick the agent and model.

The mouse works too, and the bottom bar shows the keys that work at the moment.

How it worksh2

Each tour has two agent sessions, a planner that writes the stops and a guide that answers questions, so planning never holds up an answer. The agent keeps the guide’s conversation, and each question only tells it which stops changed since it last looked.

A small background daemon owns the tours. The first tourer that needs it starts it, and it exits after 10 idle minutes. If you open the same folder in two terminals, they share one tour and see each other’s questions as they are asked.

tourer is written in Rust with ratatui and is MIT licensed. The source is on GitHub, and releases are on crates.io.