Realtime
Creators see clip and render status without refreshing. The product uses a durable event stream per user, not ad-hoc polling against the relational database for every status tick.
User WebSocket
Connect to ws://…/api/ws/user (or wss in production) with a valid access token. Events cover pipeline progress, failures, and other domain notifications scoped to the authenticated user.
Backfill cursor
Clients can pass a since cursor (aligned with Redis Streams message IDs) when reconnecting so the server replays missed events after a tab sleep or network drop. Exact query parameters are documented in the app repo and mirrored in OpenAPI where exposed.
Legacy task channel
Older integrations may still use per-task progress websockets under /api/ws/progress/<task_id>. Prefer the user-scoped stream for new work.
Example URL
On a local dev deployment: https://streamdat.neuralpromptventures.ai/api/ws/user?token=&since=