Code Tours

Code Tours walk you through a pull request in the order that makes sense to review it. Cursor reads the diff, groups related changes, and explains each group next to its code. Every pull request on Origin has a tour on its Changes tab.

Here's a tour of a pull request that moves webhook retries onto a queue:

Open a tour

What a tour gives you

Each tour is written for its pull request. A small fix might get a few sentences, while a large change gets a longer walk through its parts.

Most tours start with what the change does and why, written for someone who hasn't worked in that part of the codebase. Then the tour walks through the changes in groups and explains each one next to its code. Along the way, it points out what deserves a closer look, like behavior other code relies on. When you want more, ask Cursor about any part of the tour, or switch to Diff to see file changes only.

Terms you might not know have a dotted underline. Hover over one, or focus it with the keyboard, to see a short definition. Screenshots and recordings from the pull request description, or from the cloud agent that authored it, may show up where they help. When an agent authors a pull request, the tour may also use the agent's notes on why it took its approach, what to watch for, and what it tested.

Find your way around

• Jump to a section. Select the short lines at the top left of the tour to list its sections, then pick one.
• Share a section. Select the link icon next to a section heading to copy a link to it.
• Mark a section reviewed. Check the box next to a section to mark its files as viewed. The Diff view keeps the same progress.
• Expand a file. Test files start collapsed so the code under review comes first. Deleted, generated, and binary files may start collapsed too.

Customize a tour

To get a different tour, open the Generate custom tour menu next to the tour's title. From there, you can:

• Start with the highlights
• Choose which files the tour covers
• Set the depth
• Add your own instructions

For GitHub pull requests in a mirrored GitHub repository, everything except highlights is available.

To tour part of the pull request's history, pick a version, a commit, or a range in the version picker above the files, and the tour follows. Pick Changes since your last review to see only what changed since you last reviewed.

Ask Cursor about a tour

Select + next to a section heading to add that section to the Ask Cursor box at the bottom of the page, then type your question. To ask about a specific passage, select the text and choose Add to chat, or press Cmd ICtrl I. You'll see both when chat is available on the pull request page.

A cloud agent working on the pull request can also edit the tour. Ask it to rewrite a section, add a screenshot or recording of the change, or write the whole tour again with different instructions.

When you finish a tour

On pull requests with more than three files, a What next? card may appear after the last section. It suggests a few follow-up tours, like Changes since your last review, Files you own, or a Detailed version of this tour. Select Something else… to describe a different one. The card may also offer Add media to this tour, which asks a cloud agent to add screenshots, recordings, diagrams, or tables to the tour.

After a tour finishes loading, Is this tour helpful? lets you leave a thumbs up or down, and a comment if you want.

When tours are written

Cursor writes tours ahead of time only for repositories created on Origin and owned by a team. In those repositories, it writes the tour in the background when a pull request opens, including drafts, and when new commits are pushed. It's usually ready before the first reviewer looks.

If a tour isn't ready when you open it, Cursor writes it on the spot, and you can read each section as it appears. Tours you ask for, like a different depth or a version range, are written when you ask.

New commits

When someone pushes to the pull request, Cursor writes a tour for the new commit in the background. You keep reading the current one, and Updating… appears next to the Diff / Tour control. If you're on the latest version, the new tour replaces the old one when it's ready. If you're looking at an earlier version, select See latest when you want to move. Cursor checks with you first if you have an unsaved comment.

On an earlier version, comments on code that isn't in that version are marked Not in this version.

Large pull requests

Some pull requests are too large for a tour. You'll see Too large for a tour with a View files button that takes you back to the diff. Smaller pull requests each get their own tour.

Usage and billing

Tours that Cursor writes ahead of time don't count toward your usage. When Cursor writes a tour because you opened it or asked for one, it counts toward your Cursor usage the same way an agent request does. Reading a tour that's already written doesn't use any. When a cloud agent edits or rewrites a tour, that work counts toward the agent's usage.

Privacy

Code Tours follow the Privacy Mode of the team or person who owns the repository, like the rest of Origin. To write a tour, Cursor sends the pull request's diff and description to a model. The tour is saved with the pull request, and anyone who can see the pull request can read it.

FAQ

Related

• Pull requests - open, review, and merge pull requests
• Browse & Search - browse files, search code, and inspect commit history
• Origin - overview, access, and privacy