← All proposals

Agentic Split Button

A separate component, `AgenticSplitButton`, a copy of the PDS v2 Split Button, so the engineer's port is mostly a copy:

Net-new componentOpen in Storybook

proposals/AgenticSplitButton/context.md26 lines · View on GitHub

Agentic Split Button

Status: built 2026-10-21, ready for dev 2026-10-21 (HANDOFF.md).

Problem

The PDS Split Button (a primary action with a menu of more actions) has no agentic treatment. The Agentic Button, Agentic Menu Button and the agentic Icon Button have the AI gradient border, so a split button that offers an agent's action has nothing to match them. The design decision is that it is a new component, not an option of the Split Button.

Proposal

A separate component, AgenticSplitButton, a copy of the PDS v2 Split Button, so the engineer's port is mostly a copy:

  • the AI gradient as the border around the whole control (the primary action and the caret together), not on each half;
  • the secondary look only (there is no primary version), like the Agentic Button, so no variant prop;
  • isAnimated shimmers the border (the same loop as the Agentic Button).

Everything else is the PDS Split Button: actionItems (the first is the primary action, the rest the menu), size, iconName, placement, anchorToFullButton, moreActionsLabel.

Out of scope for now

A working state on the primary action (the Button's isWorking), a primary version, tally and status dot (the PDS Split Button hides them).

Source

The designer's decision in design review on 2026-10-21 (a separate Agentic Split Button instead of extending the Split Button). No Figma or Jira.