OpenCode Agent
SafeUser-agent: opencode
Category: AI & LLM Bots
SEO impact if blocked: 2/10
OpenCode
1 crawler operated by OpenCode
Who OpenCode is, for site owners
OpenCode operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated safe.
Blocking OpenCode carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for OpenCode: Generally safe to allow; provides legitimate crawling value.
OpenCode at a glance
| Operator | OpenCode |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
Crawler operated by OpenCode
What OpenCode's crawlers are for
OpenCode runs 1 crawler in our database. Grouped by the job each one does:
- a user-triggered agent:
opencode
The highest-priority token is Tier 3. That makes OpenCode a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat OpenCode
How often site owners write rules for OpenCode's tokens, from our own robots.txt study of the Tranco top 10,000:
| Token | Files naming it | Files blocking it |
|---|---|---|
opencode | 17 (0.3%) | Not measured |
A OpenCode token can be blocked without being named, through a User-agent: * group with Disallow: /, so its blocking share can be higher than its naming share.
All counts come from 5,583 valid files fetched October 20, 2026.
Writing one policy for OpenCode
A robots.txt file cannot say "OpenCode"; it can only name OpenCode's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything OpenCode fetches through it
User-agent: opencode
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the AI bot crawlability test after any change to see the result for each OpenCode token, including firewall refusals.
Test yourself: does User-agent: OpenCode block all of OpenCode's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token opencode.
Test yourself: if you block one OpenCode token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each OpenCode crawler, explained
A one-paragraph brief for every OpenCode token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- OpenCode Agent (
opencode, Tier 3): a user-triggered agent that fetches a page when a person asks an assistant or app to open it. Rated safe. OpenCode Agent's operator does not clearly document how it treats robots.txt. Write the OpenCode Agent rule anyway, then confirm in your logs that its requests stop. 0.3% of top-site robots.txt files name it.
Common mistakes with OpenCode's crawlers
The errors we see most often with OpenCode's crawlers in the files and firewalls we test:
- Assuming a robots.txt rule will stop OpenCode's crawlers. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
- Blocking OpenCode's crawlers as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
- Counting OpenCode's crawlers visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.
All three hide inside a file that looks correct, so check OpenCode's crawlers from outside after every change.
What our own data shows about OpenCode
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from OpenCode's marketing. OpenCode has one token in our database, so the whole picture fits in one place.
opencode in our records
We first recorded opencode on September 22, 2026. We could not find a page where OpenCode names it, so treat the token as reported rather than documented. opencode is outside our tracked token set, but 17 of 5,583 top-site files already name it, which is enough to show owners treat it as a real crawler.
Among the 104 AI and LLM crawlers in our database, opencode sits 99th by priority (Tier 3), level with AIWebIndex-Agent, alphalens-bot, amazon-QBusiness, Anomura. 81 of the 104 share its safe rating. Other operators with a crawler that fetches a page when a person asks an assistant or app to open it: ChatGPT Agent (OpenAI, Tier 1), ChatGPT Operator (OpenAI, Tier 1), ChatGPT-User (OpenAI, Tier 1), ChatGPT-User/2.0 (OpenAI, Tier 1), Claude-SearchBot (Anthropic, Tier 1). A policy for opencode is usually a policy for these too.
A decision record for opencode
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the opencode entry reads:
- Operator and job: OpenCode; it fetches a page when a person asks an assistant or app to open it.
- Priority and behaviour: Tier 3, rated safe, blocking impact low.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: opencode's operator does not clearly document how it treats robots.txt. Write the opencode rule anyway, then confirm in your logs that its requests stop.
User-agent: opencode
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the opencode entry once a quarter, or when OpenCode publishes a new token next to it.
Checking opencode on your own site
Because OpenCode runs only opencode in our records, one check covers the whole operator. Search your access logs for the string opencode over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. OpenCode publishes no page about the crawler that we could find, so judge it by the requests you actually see rather than by its name. A Tier 3 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.
How top sites treat OpenCode's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for OpenCode's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch OpenCode's crawlers too.
More questions about OpenCode
- Will blocking OpenCode affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of OpenCode's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for OpenCode?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow OpenCode on some sections and block it on others?
- Yes. Inside the group for
opencode, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking OpenCode delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether OpenCode offers a removal or opt-out process.
- Is a firewall block better than robots.txt for OpenCode?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute OpenCode review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI crawlability test to see the outcome from outside, including any firewall layer.
How to block or allow OpenCode in robots.txt
This rule covers the single crawler OpenCode operates. Add it to the robots.txt file at the root of your domain.
Block OpenCode completely
User-agent: opencode
Disallow: /
Allow OpenCode explicitly
User-agent: opencode
Allow: /
These OpenCode rules ask; they do not enforce. If a OpenCode token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about OpenCode
What crawler does OpenCode run?
OpenCode operates 1 crawler in our directory: OpenCode Agent (user-agent opencode).
Should I block OpenCode?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block OpenCode in robots.txt?
Add the following to robots.txt at your domain root: User-agent: opencode then Disallow: /.
Does blocking OpenCode hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking OpenCode does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.