Help
Where a stuck reader goes.
Community discussion, operational defect routing, vulnerability reporting, and the enterprise path for new workflows.
Discussion and integration help#
Join the Wisent Discord for integration questions and community help: discord.gg/qRjpkthq54.
Operational defects#
- Executor issues: github.com/wisent-ai/weles/issues — include the action-log row ID, worker instance ID, and release coordinate.
- Client issues: github.com/wisent-ai/weles-client/issues.
- Never place credentials, trajectories, recordings, or target details in a public issue.
Security#
Report vulnerabilities through a private GitHub Security Advisory (github.com/wisent-ai/weles/security/advisories/new, or the equivalent for weles-client). Never attach bearers, private input, credential references, receipts containing customer metadata, or production endpoints to a public issue.
Enterprise and new workflows#
New origins, new actions, trajectory design and review, deployment-ring policy, credential lifecycle integration, evidence-retention policy, and operational support are arranged with the operator. Start at weles.wisent.com or book an implementation call at calendly.com/lbartoszcze. An engagement defines the exact origins and actions; it does not grant blanket authorization to automate a website.