Feature
Telemetry and debug bundles
Usage events carry hashed workspace and org IDs and no content; debug bundles are redacted and made only when you ask.
After sync, render, validate, status, diff, pull, push and restore, the CLI posts one telemetry event: command, result, duration, CI mode and SHA-256 hashes of the workspace and org IDs. It goes to WORKLOOM_TELEMETRY_ENDPOINT (default http://localhost:4010/api/telemetry/events, a local API) and is on unless WORKLOOM_TELEMETRY_ENABLED=false.
The redaction guard rejects fields such as prompts, file contents, diffs, tokens, secrets and environment snapshots, and values that look like API tokens, absolute home paths or email addresses. `wl debug-bundle` writes a redacted bundle under .workloom/debug-bundles only when you run it.
More features
All features →- 01
Validate the manifest and its trust gates
`wl validate` checks workloom.workspace.json against the schema, then runs the trust gates over a render plan and lists what they would block.
- 02
Deterministic render plans
See every file each provider will get, with its projection policy, ownership and write mode, before anything is written.
- 03
Sync with ownership checks
`wl sync` writes only the projections the trust gate allows, atomically, and changes or removes only files Workloom owns.