Find out why a change was made

git blame tells you who and when. The session tells you why: what was tried first, what was rejected, and what the person said when they chose this

Ask Cursor why, follow its citation to the turn in the session where the decision was made. Everything below stands on its own

1. Ask

In the repository:

Why did we choose a token bucket for the rate limiter?

Distinctive words help: a function name, an error message, an issue key. The agent searches stored sessions for this repository, ranks them by how many of your terms they contain, and says for each result whether it matched the words literally or only by meaning. Treat a meaning-only match as possibly related, not as the answer

2. Follow the citation

The agent names the session and the turn. Ask for the link, or open Sessions in the web app and search the title. In the transcript reader, select the turn; the index on the left lets you filter to find it. Expand the tool results if you want to see what the agent actually ran before deciding

3. Widen when nothing matches

Recall starts with the repository you are in. If the decision was made elsewhere:

Search across all our repositories for earlier work on rate limiting

You can only find sessions you are allowed to see. A private session a colleague ran is invisible until they share it

Other ways in

• kcap sessions --touching src/ratelimit.ts lists sessions that edited a file
• kcap review <pr-url> opens a review with every session behind that pull request already loaded, which is the fastest route when the change is a PR
• The session’s Overview lists the pull requests it opened and the work item it was filed on, so you can go from a ticket to its sessions as well as the other way

Further reading

• Sessions
• Review