The back/experiment header link passes icon={<ArrowLeftIcon />} but also includes <BeakerIcon /> as the first child. Since MlflowSidebarLink already renders icon before children, this will render two icons in the expanded state; consider removing the extra icon from children (or moving it into the icon prop if that’s the intended leading icon).

Object.entries(config).map(...) returns a fragment (<>...</>) without a key, which will trigger React warnings and can cause unstable reconciliation. Use React.Fragment key={sectionKey} (or wrap in an element with key).

Telemetry for this component is logged as DesignSystemEventProviderComponentTypes.Button, but the interactive element is a navigation Link. To keep analytics semantics consistent with other link telemetry in the codebase, this should likely be TypographyLink (or the appropriate link component type) instead of Button.

The <ul> here maps menuItems to elements without providing a key on the returned top-level element, which will cause React key warnings (keys inside MlflowSidebarLink don't help because they are not on the array elements). Also, nestedItems can be a <div>/fragment, which can lead to invalid <ul> children (only <li> is valid). Wrap each entry in a keyed <li> (or a keyed fragment) and ensure the rendered children under <ul> are list items.

MlflowSidebarGatewayItems renders a top-level <div> (and nested <div> header) which will be inserted directly under the sidebar’s <ul> when nestedItems is used. That produces invalid list markup and can hurt accessibility/styling. Consider returning <li> elements (or wrapping the whole block in a single <li> containing an inner <ul>), and add an accessible label/tooltip for the collapsed header icon since it otherwise has no text.

This component returns a fragment containing <div> separators and <li> elements but does not provide an enclosing <ul>/<ol>. When it’s rendered as nestedItems inside the main sidebar <ul>, the <div>s become invalid direct children of a <ul>. Consider restructuring so that everything under the sidebar’s <ul> is <li> (e.g., wrap the whole nested block in a single <li> containing its own inner <ul>).

Pill is implemented as a clickable <div> without role, tabIndex, or keyboard handlers, so it’s not keyboard-accessible and won’t be announced correctly by assistive tech. Use a semantic <button> (preferred) or add role="button", tabIndex={0}, and handle Enter/Space, plus appropriate aria-pressed for the active state.

MlflowSidebarLink renders a <li> internally. This makes the component invalid to use outside of a <ul>/<ol> (e.g., the Docs/GitHub/Settings links are rendered inside a <div> in MlflowSidebar). Consider removing the <li> wrapper from MlflowSidebarLink and letting call sites wrap it in <li> only where appropriate (or add an asListItem/wrapper option).

This tooltip is controlled via open={isAssistantHovered && !showSidebar}, so it won’t appear on keyboard focus when the sidebar is collapsed (and it also duplicates the design-system’s own hover/focus handling). Consider using open={!showSidebar ? undefined : false} (and letting the tooltip handle focus/hover) so collapsed-icon tooltips work for keyboard users too.