Detected
Stock automation surfaces announce the agent before it reaches the work.
Undetectable browser use for AI agents
Give your AI the keys to the internet.
Weles turns authorized browser workflows into an API. It combines patched Chromium and Firefox builds, rotating fingerprints, cached trajectories, scoped credentials, recordings, and signed receipts.
- Patched Chromium + Firefox
- Cached trajectories
- Scoped credentials
- Signed receipts
- Public source
AI can write your software. It still gets stuck at the login page.
Ordinary browser agents expose automation signals, rediscover the same interface on every run, lose sessions, and leave you guessing when a workflow fails.
Slow
The same navigation is rediscovered and paid for again on every run.
Unclear
A failed action without a recording or terminal state gives you no exact point to repair.
One authorized action. One reviewed path. One recorded result.
Weles separates authorization, execution, credentials, and evidence so a browser workflow can become a production capability instead of an unowned script.
Authorize
Submit the exact origin, action, justification, idempotency key, and credential references.
Resolve
Weles selects the reviewed trajectory and the verified Chromium or Firefox artifact.
Execute
The worker replays the route with a coherent browser identity and scoped credentials from Skarbiec.
Prove
The action closes with terminal state, retained evidence, and—when configured—a signed receipt verified offline.
Real runs, not a browser mockup
The public Weles repository includes redacted recordings from production actions on GitHub, Reddit, and LinkedIn.
| Target | Action | Recorded result |
|---|---|---|
| GitHub | Sign in | Authenticated dashboard reached |
| Credential flow | Stored session later confirmed healthy | |
| Sign in | Authenticated home feed reached |
Inspect the executor, the browsers, the client, and the benchmark
The Weles executor, client, Chromium patch series, Firefox patch series, and comparison benchmark are public repositories.
| Repository | Owns |
|---|---|
| weles | Executor, trajectories, worker and admission API |
| weles-client | Submission client and signed receipt verification |
| weles-chromium | Chromium patches, build instructions and published artifact |
| weles-firefox | Firefox patches, build instructions and published artifact |
| probierz benchmark | Versioned comparison against other browser-agent systems, from the suite in weles/benchmark |
The browser can reach a page. That does not grant permission to automate it.
Does Weles authorize automation of a target?
No. Authorization remains with the operator and every production submission must name its exact origin, action, and justification.
Do passwords enter the agent prompt?
No. Credentials resolve through scoped Skarbiec grants and are kept out of prompts and logs.
Is the source public or only the client?
The executor, client, patched-browser repositories, and benchmark are public. The operated service adds provisioning, reviewed trajectories, evidence retention, and support.
Turn the next browser workflow into an API.
Start with one exact origin and one exact action. Weles turns the approved journey into a repeatable trajectory with bounded credentials and recorded evidence.