---
schema_version: "newruntime-reader-dossiers-v1"
type: "reader_dossier"
slug: "unidentified-linux-chrome"
kind: "unidentified"
operator: "unknown"
researched_at: "2026-10-23"
confidence: "low"
json_url: "https://newruntime.com/readers/unidentified-linux-chrome.json"
canonical_url: "https://newruntime.com/readers/unidentified-linux-chrome/"
---

# Unnamed Linux-Chrome automation

> Clients presenting a desktop Chrome on Linux user agent that the observatory classifies as automation rather than a human browser. No product name, operator or documentation is visible in the published label.

## Dossier

- Kind: Unidentified
- Operator: unknown
- Documentation: none found
- robots.txt tokens: none documented
- Feeds: unknown
- Respects robots.txt: Not documented. Unknown: a generic browser string cannot be addressed by name in robots.txt.
- Verification: Unknown
- Labels matched in our logs: unidentified-linux-chrome

## Why it matters to New Runtime (our interpretation)

Headless-browser traffic like this is usually scraping or an agent rendering pages; it reads like a person but never runs page assets, so it stays out of human counts.

## Observed behaviour

- Baseline 2026-10-23 (93-day window): 1,025 requests on 8 days; first seen 2026-10-13, last seen 2026-10-23; Regular.
- Live numbers: https://newruntime.com/bot-traffic-history.json and https://newruntime.com/crawler-journeys.json

## Sources

- No public source found; the dossier describes only what the client declares and did.

Identity: A family name is what a client claims in its user agent. It is verified only when its request came from the operator's published IP ranges or passed forward-confirmed reverse DNS, as reported per family in /crawler-journeys.json. Anyone can claim any name.

All dossiers: https://newruntime.com/readers.md