Key request sequences
Time moves from top to bottom. Vertical lines represent participants; arrows represent calls or responses. Use these diagrams when following network logs or API code.
File upload
The API's registration response and video processing completion are separate events. See state transitions for subsequent indexing. Files of at least 100 MiB use multipart upload instead of one signed URL, and uploaded files are transcribed through separate interval jobs.
Browser login
Better Auth runs at the API's /api/auth/*. This is separate from issuing and refreshing OAuth tokens for MCP.
Asking about a course
Text and citations can arrive before generation finishes; done follows answer persistence. The browser applies queued content on animation frames and enables feedback after completion. Metadata-only answers skip scene embeddings and have no scene citations. Non-streaming chat.send returns the same structured answer after saving. Without a course, the response has no tools or course history record.
Related: Authentication and access control, Prompt design.