Skip to main content

Documentation Index

Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

A conversation request has two lanes. The live lane streams output to Studio over SSE. The durable lane records messages, run status, and run events in the API.

​
Main steps

  1. Studio writes conversation state: Studio uses REST routes for conversations, messages, branches, participants, and read state.
  2. Studio starts agent work: Studio calls an AG-UI route on veryfront-agent for default chat, or starts a canonical run before attaching to the run SSE stream for project-agent work.
  3. The agent validates context: veryfront-agent authenticates the bearer token, validates the request body, and checks project access when the request has a project.
  4. The durable run starts: The agent creates or reuses a durable run through the API. In durable root-run flows, it persists the latest user message before creating the run.
  5. Output streams live: AG-UI chunks update Studio over SSE while the model or project runtime runs.
  6. Events persist durably: The mirror converts stream chunks into run events and appends them through REST.
  7. Streams resume from durable events: Studio attaches to /conversations/{conversation_id}/runs/{run_id}/stream with Last-Event-ID when it needs replay after a reconnect.
  8. Clients catch up: Studio listens for WebSocket lifecycle notifications, then reads current state through REST when needed.

​
Next