Code
Code is a bot operated by GitHub Copilot that pulls documentation and examples while an AI writes code. Code (GitHub Copilot) is an AI coding agent that can autonomously plan, build, and execute development tasks, functioning as a collaborative AI pair programmer. 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.
Code at a glance
| User agent | CodeToken only. The operator has not published a full user-agent string, so match on the substring rather than an exact header. |
|---|---|
| Operator | GitHub Copilot |
| Purpose | Coding agents |
| Respects robots.txt | Not documented |
| Verification method | None 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 | Code |
| Operator documentation | None published |
Code (GitHub Copilot) is an AI coding agent that can autonomously plan, build, and execute development tasks, functioning as a collaborative AI pair programmer.
Allow or block Code
Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.
User-agent: Code
Disallow: /Blocks every path for this crawler only.
User-agent: Code
Allow: /Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.
User-agent: Code
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own account, checkout and search URLs.
What blocking actually costs you
Blocking Code mainly affects developers reading your documentation through an AI tool. Most sites want that traffic.
Block every crawler in the directory at onceIs that really Code?
A user-agent header is a string the client chooses. Scrapers copy Code precisely because site owners allow it. 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.
Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.
Related crawlers
Identify crawlers automatically instead of by hand
Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.