Coding agents
Cursor is a bot that pulls documentation and examples while an AI writes code. Cursor is an AI coding agent that helps write, edit, and understand code. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"Cursor"
Checked against
Nothing published
Live check
No operator check exists for Cursor. This still shows what the address really is.
Reference
| User agent | CursorToken only: match on the substring. |
|---|---|
| Operator | Cursor |
| Purpose | Coding agents |
| Respects robots.txt | No policy |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | Cursor |
| Operator documentation | None published |
Cursor is an AI coding agent that helps write, edit, and understand code.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: Cursor
Disallow: /User-agent: Cursor
Allow: /User-agent: Cursor
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Cursor mainly affects developers reading your documentation through an AI tool. Most sites want that traffic.
Build a file for every crawlerFAQ
Cursor is a bot that pulls documentation and examples while an AI writes code. Cursor is an AI coding agent that helps write, edit, and understand code. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Not documented. No operator statement says whether Cursor reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the Cursor token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking Cursor mainly affects developers reading your documentation through an AI tool. Most sites want that traffic.