feat: Support IDE chat global state

Frédéric Capletterequested to merge
fc-implement-chat-global-state-for-ide into main

What does this MR do?

To allow the IDE to show an info banner at the top when there are conccurent connections on the same Flow happening, we add the same structure as what we did for the web agentic chat, which is to add a chat-state prop that allow user to pass an enabled/disabled state with a reason message.

Screenshots or screen recordings

Before After
Screen Recording 2025-12-05 at 14.44.32.mov Screen Recording 2025-12-05 at 11.58.21.mov

Integration merge requests

How has this been tested?

  1. Setup Duo Agent Platform locally in GDK https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/duo_agent_platform.md
  2. Enable the feature flag duo_workflow_lock_concurrent_flows
  3. Recompile workhorse with cd workhorse && make && gdk restart workhorse
  4. Check with the latest change in LSP gitlab-org/editor-extensions/gitlab-lsp!2658 (merged). To test this, pull the duo ui branch locally, and then use yalc. The steps for yalc
    1. npm i yalc -g
    2. In the Duo-ui repository, yarn run build && yalc publish
    3. in the LSP repository, yalc use @gitlab/duo-ui@15.0.4 (Change the version to match your package name)
    4. In the Duo Agentic chat root package: yalc use @gitlab/duo-ui@15.0.4
  5. Start the Extension host debugger inside the LSP project
  6. Start a new agentic chat
  7. Open a new tab in the IDE and then open agentic chat in the web. It should show the same chat you just messaged in the first tab
  8. Send another message in the first tab on the web
  9. Once it's running (Duo replied one message like reading an issue), send a message immediately in the IDE
  10. The IDE will show an info banner message at the top that anoteh chat is running. The Input is also disabled and new messages are shown every 3 seconds
  11. Once the Web chat flow finishes, the message disappear and the input is available.

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by Frédéric Caplette

Merge request reports