Decisions: AgenticMenuButton

A separate component, not a Menu Button option (2026-10-21)

• Decision: the agentic menu is its own component, AgenticMenuButton. It is a copy of the Menu Button component with the trigger fixed: the AgenticButton in label mode (always the secondary look), and an IconButton with variant='agentic' in iconOnly mode. isAgentic and variant were removed from it; isAgentic was also removed from MenuButton, which keeps its other changes. It reuses the Menu Button's CSS and NavAccordion, and adds the class pds-agentic-menu-button to the root.
• Why: the designer decided the agentic menu and split buttons are new components, not extensions of the existing ones.
• Port impact: one new component, which imports AgenticButton, the Icon Button's agentic variant, and the Menu Button's CSS and accordion, so it ports after those. MenuButton needs nothing for agentic.
• The icon-only open state needs a small CSS override (agentic-menu-button.css), moved over from the Menu Button, so the open (expanded) state still shows a fill on top of the gradient border.

Dependents

• Labeled Divider: its selector uses the AgenticMenuButton for the agentic tones and the plain MenuButton for neutral.

Open questions

• The copy repeats the whole Menu Button logic (about 850 lines). Should the port instead let Menu Button take a trigger, and keep the agentic menu as a thin wrapper? That would reintroduce a prop on Menu Button.
• Should the agentic menu offer a mobile accordion at all? It is copied as is.