opencode user agent
Operated by SST (opencode)
opencode is a user agent reported for opencode, an open source AI coding agent.
The opencode bot at a glance
- opencode is operated by SST (opencode) and loads web pages in a browser to complete tasks on behalf of a user.
- The robots.txt token for opencode is opencode.
- Blocking an AI agent has no effect on search rankings.
- opencode robots.txt support: Not documented.
- Recommendation for Generative Engine Optimization (GEO): Your choice.
What is opencode?
opencode fetches web pages while a developer’s agent works on a task.
Its robots.txt behaviour is not documented.
Should you block opencode?
Blocking opencode is a business decision: it protects your content but can lower how well AI products know your brand.
| Effect on search rankings | Blocking an AI agent has no effect on search rankings. |
|---|---|
| Effect on AI visibility | Blocking stops agents from completing tasks on your website for their users, which can cost bookings or sales that agents would have made. |
| Follows robots.txt | Not documented |
| Recommendation | Your choice |
How to block or allow opencode
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token opencode is matched case-insensitively. robots.txt alone may not stop opencode, so add the Nginx, Apache or Cloudflare rule as well.
robots.txt: block
# Block opencode
User-agent: opencode
Disallow: /robots.txt: allow
# Allow opencode
User-agent: opencode
Allow: /robots.txt: partial
# Keep opencode out of private areas only
User-agent: opencode
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to opencode
if ($http_user_agent ~* "(opencode)") {
return 403;
}Apache
# Apache .htaccess: return 403 to opencode
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (opencode) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "opencode")How to verify real opencode traffic
SST (opencode) publishes no IP list or reverse DNS pattern for opencode, so the user agent cannot be verified. Anyone can send the same string. Rate-limit unusual volume instead of trusting the name.
How to find opencode in your server logs
Search the web server access log for the token. The command below counts opencode requests per URL on Nginx or Apache.
grep -i "opencode" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
opencode FAQ
opencode uses the robots.txt token "opencode". SST (opencode) does not publish a full user-agent string, so match the token inside the User-Agent header.
SST (opencode) has not documented how opencode treats robots.txt. Add a robots.txt rule and back it with a server rule if the traffic matters to you.
Blocking an AI agent has no effect on search rankings. Blocking stops agents from completing tasks on your website for their users, which can cost bookings or sales that agents would have made.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: opencode" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. SST (opencode) publishes no IP list or reverse DNS pattern for opencode, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "opencode", for example with: grep -i "opencode" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Public bot registry. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
