feat: add gated agent sessions with follow-ups and live tool traces

[devhims]

The agent API already supports durable conversations, but the dashboard cannot open or continue them. This adds a gated Sessions view for searching history, starting requests, and sending follow-ups with the existing conversation context.

• Return sessionId in API receipts, runs, and session responses. Keep conversationId as a deprecated request alias and preserve stored IDs and Durable Object identities. Clients reading conversationId from responses must update, including clients using the legacy response format.
• Use the existing verified-email agent access check for the sidebar, direct pages, and every backend endpoint. Each account sees only its own sessions.
• Stream persisted phase changes and tool activity over an authenticated SSE endpoint. Reconnection restores the same run; ambiguous submission retries reuse their message and idempotency key. Display tool inputs, status, timing, and bounded evidence summaries. Deliver the validated answer with citations when finalization completes.
• Document the API contract and add route, runtime, stream-parser, and browser coverage. Generated reports, screenshots, and traces remain local and are excluded from the PR.

Streaming follows the support-agent UI pattern: progress and tool results arrive during execution, and the validated answer arrives at completion. It does not expose raw model tokens or reasoning. The observer reads durable snapshots every second and rotates its connection after 25 seconds to recheck access. Existing execution deadlines and model configuration are unchanged.

Validation: platform and live-test TypeScript checks; 493 platform unit/contract tests; 26 local Durable Object/account integration tests; 16 processor tests; 31 web unit tests; six browser scenarios using local fixtures and Chrome; web webpack production build; generated OpenAPI check. Browser coverage includes follow-up retry after uncertain admission, mid-run stream disconnect, page reload, trace restoration, failed runs, access denial, and mobile layout. No live inference or production deployment was needed for these checks. The default local Turbopack build encountered an environment port-binding restriction; the webpack production build passed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
video2ctx-web	Ready	Preview	Sep 11, 2026 10:40am UTC