Help readers evaluate the product before installing
This historical note records the addition of a public documentation and article surface. A device-access service asks users to connect real computers and authorize actions, so a short slogan is insufficient. Readers need to know where work executes, which data passes through the service, and how to stop or narrow access.
The current site separates practical guides, explanations, reference and product changes. New readers can start with why the agent and execution device are separate, then complete the first-device guide. Developers integrating ADC can use the CLI, tool and API references instead of reconstructing behavior from screenshots.
Make useful information discoverable
Public routes have their own titles, descriptions and canonical URLs. The same route catalog supplies statically rendered pages, a sitemap and a release/article feed. This gives readers stable links and helps crawlers find the pages; it does not guarantee search ranking or prove a technical claim.
Machine-readable llms.txt resources summarize the public material for tools that choose to consume them. They do not connect an agent to a device or bypass authorization. An integration still needs an account, a grant and a supported client path.
Explain data handling alongside setup
Local execution means tools run on the selected device; it does not mean requested data never reaches the control plane. The public privacy explanation covers account records, disclosed device metadata, requests and results. Optional website analytics is a separate feature with a small route and onboarding event catalog.
Source builds do not configure a project analytics destination by default. An operator must explicitly configure the provider to enable it, and the browser checks GPC and Do Not Track first. This default concerns website analytics; it does not disable the task records required to operate the service.
Keep explanations tied to shipped behavior
Documentation lives with the implementation so a tool change can update its instructions in the same review. A useful guide states prerequisites, commands, expected results and failure handling. An engineering article explains the mechanism and its limits. A release note describes user impact and upgrade compatibility.
This page remains at its historical URL for existing references, but the main article index prioritizes product explanations and current release notes. For today's supported behavior, use the current reference and changelog. Windows Node and Android Node are still marked as testing there; publishing documentation does not change their maturity.