Operator Path: Browser to Gateway

Operator Path: Browser to Gateway A sequence diagram generated by Archify. GET / forward to app GET /operator/session Server-side, via a Caddy alias identity or 401 page, or 302 to login GET /operator/auth/github/start proxy over the VPC 302 to GitHub Responses travel back throughCaddy authorize redirect with code GET /operator/auth/github/callback proxy over the VPC exchange code, read user session cookie, 302 back GET /operator/runs/:runId/stream proxy, no buffering event: ready, then frames Page load Sign in Run stream Browser · operator · Sequence participant Browser operator Dashboard Caddy · TLS + /operator/* · Sequence participant Dashboard Caddy TLS + /operator/* Dashboard app · UI on :3000 · Sequence participant Dashboard app UI on :3000 Gateway listener · session, OAuth, SSE · Sequence participant Gateway listener session, OAuth, SSE GitHub OAuth · identity · Sequence participant GitHub OAuth identity Legend main request return security async trace message