[Experiment] Add the Duo home page app with embedded chat and a sessions feed

Stack (merge in this order)

Order MR Change
1 Sync routes for gitlab-org/gitlab!269673 (Duo home dashboard) HTTP router route sync
2 Add a flag-gated Duo home route and homepage preference Backend: flag, route, gate, homepage preference
3 Add the Duo home page app with embedded chat and a sessions feed Frontend: page app, embedded chat, sessions feed (this MR)

What does this MR do and why?

Adds the page app for an experimental Duo-first home page at /dashboard/duo_home, behind the sdlc_duo_home feature flag (wip, default off) for internal testing. The flag, route, gate, and homepage preference moved to Add a flag-gated Duo home route and homepage preference on review. This MR targets that branch, so its diff is the frontend only. Part of SDLC Chrome and Panel Readiness.

The commits read in order: the embedded chat surface, the sessions feed, the page app and its layout, and the prompt's gradient styling. The rest follow review: the prompt glides into place when sessions load, the page keeps the chrome's breadcrumb trail, the server leaves interactive CLI sessions out of the feed, the empty-feed spec waits for the absence, sessions link by their web path, the page app moves under ee/, and two changes follow new master lint rules. The split kept the commits reviewers already read instead of squashing them, so the series runs past the 10-commit guideline.

The page renders only where the backend's gate passes: the feature flag and the access_duo_agentic_chat ability. It no longer also requires Duo's "Experiment and beta features" setting, because the Duo panel's session inbox it mirrored dropped that requirement when it became generally available (Make Duo panel session inbox generally available).

The page is one centred column on the shared BaseLayout, bounded to the panel chrome's --panel-content-inner-height, with a static screen-reader-only page heading.

  • The prompt is an embedded Duo agentic chat in a reduced presentation, a fresh session per visit. It is the light agentic chat manager, which holds its own workflow stream so it shares no live state with the AI panel (that change is Give the light agentic chat manager its own workflow stream); this MR adds the page's chat wrapper, router, and surface. If the chat chunk fails to load or its configuration is unusable, the page shows a short "couldn't load" message in its place. The prompt is lit by the brand AI gradient, as a hairline on the input and a soft halo behind it; the composer keeps the Pajamas focus ring. The model selector and the Agentic toggle stay in the AI panel.
  • Sessions that need the user sit below the prompt, on the shared FocusCarousel: agent sessions in the awaiting-input status group (input, plan approval, tool approval), newest first. Archived sessions (past checkpoint retention) drop. Interactive Duo CLI sessions are left out on the server, with the same rule and retention cutoff as the Duo panel inbox's "Needs a decision" tab (Add excludeSourceTypes to duoWorkflowWorkflows): they are answered in their terminal, and idle ones sit in INPUT_REQUIRED after the terminal closes. Row-level errors keep partial data; the feed refetches when a session opens in the panel or the tab regains focus, and never polls. Duo Chat threads, running, and finished sessions are not shown.
  • With nothing that needs the user, there is no feed and no empty-state text: the prompt sits centred in the column. For most users this is the page, since today awaiting sessions come mostly from custom flows. Sessions load after the first paint, so when some arrive the prompt glides up from the centre to its place instead of jumping there (at once under reduced motion).
  • Starting a chat moves the page into a distraction-free state: the feed leaves and the composer travels down with the transcript, respecting reduced motion. To get back, type /new (Duo Chat's existing command, also /reset or /clear): an emptied thread returns the page to its landing state. Selecting Home or the GitLab logo does the same. There is no visible "New chat" control on the page yet, because the panel's one lives in the chat header, which the embed hides; a visible control is a candidate follow-up.

The page uses the chrome as it is: the "Your work / Duo home" trail shows in the panel header, or in the topbar under page_breadcrumbs_in_top_bar, which is why the table below shows both chromes.

Screenshots or screen recordings

This MR adds a new page, so there is no before, except in the last row, which compares the previous head. Each row is one state of /dashboard/duo_home on this branch, in both chromes: production's default (page_breadcrumbs_in_top_bar off) and breadcrumbs in the topbar (flag on). Rows with sessions seed three awaiting sessions plus three that must not appear (a running flow, a finished flow, and an idle CLI session); the "nothing needs you" rows seed only those three.

State Default chrome Breadcrumbs in topbar
Sessions need the user, dark mode, 1440x900 01_populated_dark 01_populated_dark_topbar
Sessions need the user, light mode, 1440x900 02_populated_light 02_populated_light_topbar
Nothing needs the user: centred prompt, dark mode, 1440x900 03_nothing_needs_you_dark 03_nothing_needs_you_dark_topbar
Sessions need the user, narrow, dark mode, 390x844 (the feed scrolls at this height, so "Up next" and the counter sit below the fold) 05_narrow_dark 05_narrow_dark_topbar
Nothing needs the user, narrow, dark mode, 390x844 07_nothing_needs_you_narrow_dark 07_nothing_needs_you_narrow_dark_topbar
Chat failed to load, over a live feed, dark mode 04_chat_unavailable_dark 04_chat_unavailable_dark_topbar
The prompt in close-up: halo and gradient hairline 06_prompt_halo_detail
The composer focused: Pajamas ring plus the lit hairline 07_composer_focused
After the first message: distraction-free chat, then /new back to the landing state (local GDK against the agent platform) dark_1440_after_send dark_1440_after_new_chat
The whole loop: centred prompt, first message, reply, /new (video, 1440x900)
Sessions arriving 1.5s after the page paints: the previous head jumps the prompt to the top in one frame, this branch glides it there (video, 1440x900, dark)

How to set up and validate locally

Enable sdlc_duo_home for a user with agentic Duo Chat, set Preferences > Behavior > Homepage to "Duo home", and visit /dashboard/duo_home.

With no sessions awaiting input, the page is the centred prompt. To get a session that needs you: start an agent flow from the AI panel or an Agents Platform page and let it ask for an approval or an answer. Duo Code Review runs, running flows, and Duo Chat threads deliberately do not appear. Send a prompt to enter the chat, then type /new to return.

Jest covers the page suites under both Vue 2 and the Vue 3 compat build. The EE feature spec runs axe scans against the page with and without sessions, asserting that sessions which do not need the user never render. The gate's request, controller, and helper specs are in Add a flag-gated Duo home route and homepage preference.

Edited by Paul W

Merge request reports

Loading
Loading