From no Weles state to one observable navigation result.
Build the CLI from its public source, confirm the installation, walk the first-use onboarding boundary, and produce your first fingerprinted navigation with captured output. Everything here runs locally; no hosted endpoint is required until you integrate the client.
The executor ships as public source and as immutable worker-v* release artifacts promoted through candidate, development, canary, and production rings. There is no registry package today, so install from a source checkout and record the commit you built:
Shell
git clone https://github.com/wisent-ai/weles
cd weles
npm install
npm run build
npm install --global .
Onboarding explains what Weles will and will not execute before any browser automation runs. It never launches browser automation itself.
Run weles onboarding status — it prints the current journey screen as JSON and starts at the authorization-boundary screen.
Run weles onboarding next to reach the optional existing-data screen. Import a real Weles trajectory API export with weles onboarding import <trajectory-export.json> --host <managed-worker-hostname>, or run weles onboarding next again to keep an empty usable setup.
The import operation validates the complete export before writing, returns every item as imported, unchanged, or refused, and advances onboarding only after the destination confirms at least one imported or already-persisted definition.
Continue through the host-execution screen. Finish later with weles onboarding verify --receipt <receipt.json> --keys <receipt-keys.json>: completion requires cryptographic verification of a real workflow receipt and its bound evidence digest, which only a real production run can produce.