SeeRepo with Cursor

Cursor writes code with you, in the editor or with its cloud agents. SeeRepo shows you what it changed and how it connects.

The signature it leaves

Cursor's agent adds a "Made with Cursor" line to commits and pull requests, on by default and changed in its Attribution setting (Cursor and Git). Cloud agents need a paid plan and work on their own branch (Cloud agents). Cursor doesn't document the author address or the branch prefix of those commits.

How SeeRepo recognizes it

A commit counts as Cursor's when its author or its Co-Authored-By line has a cursor.com address, an address that starts with cursor@ or cursoragent@, the words "Cursor Agent", or the "Made with Cursor" line. A merge of a branch that starts with cursor/ also counts.

Where it shows in SeeRepo

• Made by, on a part's sheet: its logo next to the people. Click it and the map shows only what Cursor touched.
• Journey: its posts tell, day by day, what it did, with its mark; Who wrote it, on the wall, what share it signed since the start. Tap it there to open its sheet: what it fixed, what it left and which modules it worked on this month, with the link to its posts. See Journey.
• Moments: the day it starts writing most of the project, the moment "Cursor took over from …" stays.
• The filter: under Agent, pick Cursor to see only its work.

The full list of agents SeeRepo recognizes is in the Agent directory.

Hand it a prompt from SeeRepo

SeeRepo writes prompts for what's worth fixing, ready for Cursor:

1. Open Health and tap a task: failing tests, errors in production, packages with security flaws, files nothing uses… Its sheet opens. See Health.
2. Click "Copy prompt". The prompt names your repo, lists the files, and says what to do.
3. Paste it into Cursor: it will know which files to read.

If your project has no automatic tests, Health says so in Tests ("They don't run on their own") and offers "Copy prompt to make them run on their own": Cursor can set them up in a few minutes.