Other agents SeeRepo recognizes

Besides the agents with their own page, SeeRepo recognizes 18 more. Each one counts by the signature its makers document: its name or address as the author of the commit, in a line at the end of the message (Co-Authored-By, Assisted-by…), or the branch it opens.

The rules

Agent	A commit counts when it has…	Also by its branch	Where it's documented
Devin	devin-ai or a cognition.ai address	devin/	Devin and GitHub
Jules	google-labs-jules	jules/	Jules changelog
Gemini	the word "gemini"	—	GitHub docs
Aider	the word "aider"	—	Aider's code
Amp	an ampcode.com address	—	Amp settings
Factory	factory-droid	—	Droid settings
OpenHands	[email protected] or openhands-ai[bot]	—	OpenHands settings
Warp	[email protected]	—	Warp's spec
Qwen Code	[email protected]	—	Qwen Code's code
Crush	Assisted-by: Crush or [email protected]	—	Crush's code
Continue	[email protected]	—	Continue's code
Mistral Vibe	[email protected]	—	Mistral Vibe's code
Junie	junie-agent	junie/	Junie's GitHub action
Kilo Code	kiloconnect[bot]	kilo/	Kilo Code's code
opencode	— (only its branch)	opencode/	opencode's code
SWE-agent	[email protected]	—	SWE-agent's code
Sweep	sweep-ai[bot]	sweep/	Sweep's repo
CodeRabbit	coderabbitai[bot]	—	CodeRabbit docs

"Also by its branch" means that merging a branch whose name starts that way counts its commits as that agent's.

What their makers say

• Devin: who authors the commits is a setting: they can carry Devin's name or yours (Devin and GitHub). When they carry yours, SeeRepo counts them as yours.
• Gemini and Aider: SeeRepo reads the word in the author or in a line at the end of the message.

The ones that leave no signature

Cline, Roo Code, Goose, Zed, Kimi CLI, Grok Build, Augment Code, Qoder, Trae, Tabnine, Kiro, Base44, Emergent, Firebase Studio and Manus write code too, but their makers don't document a mark in the commit: their commits carry your name. SeeRepo counts them as yours, and each one is in the Agent directory with the source that was checked. When one of them documents a signature, SeeRepo learns it.

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 that agent 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 "Devin took over from …" stays.
• The filter: under Agent, pick one of them 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 your agent:

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 your agent: 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": your agent can set them up in a few minutes.