ASK Frontend Service — Overview¶
The Frontend Service is the web UI of the ASK platform — the Next.js application that end users interact with. It renders the chat interface, agent management screens, organisation settings, and knowledge base management. It is a stateless single-page application: all state lives in Core Service and is fetched via API.
What it does¶
| Responsibility | Detail |
|---|---|
| Chat interface | Renders conversations, streaming LLM responses, tool outputs (code blocks, charts, tables), and file attachments |
| Agent management | Create, edit, and delete agents; configure system prompts, enabled tools, and default model |
| Organisation settings | Invite users, manage roles, configure enabled AI models per org, set feature flags |
| Knowledge base UI | Upload documents, browse ingested files, trigger re-ingestion |
| Authentication | Redirects unauthenticated users to Zitadel (sso.ask.mod.auh1.dev.dir) and handles the OIDC callback |
Integrations¶
| System | Role |
|---|---|
| Core Service | Primary API — all data (users, agents, models, orgs) fetched from https://core-service.ask.mod.auh1.dev.dir |
| Zitadel | SSO — login page hosted at sso.ask.mod.auh1.dev.dir; frontend holds the OIDC session cookie |
| Hatchet | Indirectly — async jobs (file ingestion, bulk ops) are triggered via Core Service API calls |
Login domain baked into image
The staging image has NEXT_PUBLIC_APP_BASE_URL=ask.stg.ai71.ai baked in at build time, which redirects unauthenticated users to admin.ask.stg.ai71.ai instead of the local Zitadel. An air-gap rebuild is required to point the frontend at the correct SSO domain. Until then, access the platform via https://ask.mod.auh1.dev.dir with a pre-authenticated session.
Pages in this section¶
| Page | Purpose |
|---|---|
| Frontend Deployment (ASK Web UI) | Deploy runbook — image mirroring, Helm values, ingress, TLS, known login redirect issue |