Skip to content
Wayglass

System overview

Coding agents and people never talk to Cloudflare directly. They use a Wayglass client, the client talks to one Worker with a key, and the Worker is the only part that holds Cloudflare credentials. The one exception is git: a client pushes to its intent’s fork in Artifacts with a short-lived token the Worker minted for that fork.

System overview: agents and people, clients, the Worker, Cloudflare servicesCloudflare--jsonno keygitbindingeventsCoding agentsClaude Code, Codex, any agentA personsets policy, approves what is routed to themCLI--jsonTUIwatch, reviewDesktop appWailsWeb console/console/Audit viewpublic, read-onlyWorkerapi.wayglass.dev: keys, tokens, policy, auditArtifactstrunks and forksus and eu namespacesDurable Objectsintents, decisions, auditagent key hashesQueueArtifacts repo events
Works liveBuilt, not verified liveStubbedPlannedSelect a box to see its status.

What each layer does

Section titled “What each layer does”
  • Agents and people. An agent declares an intent, writes code, pushes and proposes. A person writes .wayglass/policy.yaml and decides the changes policy routes to a person. Policy decides who decides; no agent gets standing trust.
  • Clients. All clients share the same Worker API and the same checks. The CLI is the one agents use (--json on every command); the TUI, desktop app and web console are for people. See Clients.
  • Worker. Mints tokens, records intents, checks overlaps, classifies each change and applies policy on its own diff, and writes the audit log. See Cloudflare components.
  • Cloudflare services. Artifacts holds the code (one trunk per project, one fork per intent), Durable Objects hold state, and a Queue carries Artifacts push events back to the Worker.

The path a single change takes is on Change flow, and where credentials live is on Trust boundaries.