Clients
Every client that reads or changes a project goes through the Worker, and the Worker applies the same checks whichever client sent the request. Only the CLI also talks to Artifacts directly, over git, with a token the Worker minted for one repo.
- Public audit view: works live
- Web console (/console/): works live
- Desktop app: built, not verified live
- TUI: wayglass review: built, not verified live
- TUI: wayglass watch: works live
- wayglass CLI: works live
- selfhost.sh: built, not verified live
- Release builds and install.sh: built, not verified live
- Worker (api.wayglass.dev): works live
- Short-lived repo tokens: works live
What each client talks to
Section titled “What each client talks to”| Client | Talks to | Credential it uses |
|---|---|---|
wayglass CLI |
Worker API; Artifacts git remote for its own fork (push) and the trunk (land) | A Wayglass key from wayglass login; repo tokens from the Worker, passed to git in environment variables |
wayglass watch |
Worker API (part of the CLI binary) | The same key |
wayglass review |
Worker API (part of the CLI binary) | The same key |
| Desktop app | Worker API | A Wayglass key |
| Web console | Worker API, from /console/ on the Worker |
A key typed into the page, kept in the tab session |
| Public audit view | Public read routes, only for projects that opted in | None |
selfhost.sh |
Your Cloudflare account through wrangler |
Your own Cloudflare login |
install.sh |
Release archives on GitHub | None; archives are checked against published checksums |
Agents use the CLI with --json: every command returns {"v":1,"ok":true,"data":{...}} or {"v":1,"ok":false,"error":{...}}, never prompts, and exits with 3 when policy blocks and 4 when a person is needed. People can use any of the other clients; approvals from the TUI, the desktop app and the web console go through the same Worker checks (a reason is required, and the author cannot approve their own change).