What Weles owns#

Weles owns authorized stealth browser automation end to end. A caller submits one approved workflow — an exact origin, an exact action, non-secret input, opaque credential references, and a human-readable justification — and a worker on an approved host executes it in a verified browser build.

The executor combines custom C++-patched Chromium and Firefox forks with rotating fingerprints to keep agents out of CAPTCHA loops and away from bans. Every crawl is mapped into a trajectory, so later approved runs replay the cached traversal instead of rediscovering how the website works. Failed runs are recorded with the exact point of failure marked.

Every run closes with a terminal action-log state. Deployments with receipt issuance add a signed outcome and evidence digest that the public client verifies offline, without reading worker logs.

The surface this documentation describes#

weles CLI — local onboarding through the authorization boundary, durable import of existing Weles trajectory exports, fingerprinted navigation (open, screenshot), Google Workspace delegation, diagnostics (doctor), and offline receipt verification (onboarding verify). This site documents weles 0.6.5.
@wisent-ai/weles-client — the public Node.js library that submits authorized workflows, reads status, cancels tasks, and verifies signed receipts. Its minimum public contract is 0.1.0.
Scheduler and action log — task admission, lease-and-claim placement on approved hosts, and terminal state.
Signed receipts — schema weles.receipt.current binding task, organization, origin, action, outcome, and evidence digest to a trusted signing key.
Capture artifacts — screenshots, extracted body text, and failure recordings retained by the service.

Operated service, public source#

Weles is an operated service: access starts with a deployment that provides an endpoint, an organization identifier, and an organization-scoped token. Both the executor and the client are public source (executor MIT, client Apache-2.0), so you can inspect and operate your own deployment. A source checkout does not include a hosted endpoint, approved trajectories, managed credentials, evidence retention, or an SLA — those are provisioned separately for each organization.

Draft discovery can map a new journey, but it does not authorize that journey as a production action. Authorization for the target remains with you: a technically successful run does not establish that the target permits automation.

Where to start#

Quick start — install from source, confirm the installation, optionally import existing Weles workflow definitions, and reach one observable navigation result.
Concepts — workflow, scheduler, trajectory, session, fingerprint profile, and receipt, defined once each.
CLI reference — every command and argument on weles 0.6.5, checked against the binary's own help output.
Client reference — submit, status, cancel, and offline receipt verification with @wisent-ai/weles-client.
Command surface — every leaf invocation of the CLI, the MCP tools and the worker action catalog at one measured revision, the capabilities that replace the verb-per-incident families, and the order in which they land.
Troubleshooting and limits — observed failure codes, diagnostic phases, and the limits with their numbers.