← All proposals

Agentic Button

A separate component, `AgenticButton`, for an action the agent does:

Net-new componentOpen in Storybook

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

Agentic Button

Status: built 2026-10-21, ready for dev 2026-10-21 (HANDOFF.md). Replaces the isAgentic option of the Button proposal.

Problem

The Button proposal carried the agentic treatment as an isAgentic option on every Button, on top of the primary and secondary variants. The design decision is to make the agentic button its own component instead, and for it to use the secondary treatment, not the primary one.

Proposal

A separate component, AgenticButton, for an action the agent does:

  • the secondary Button look (surface fill) with the AI gradient as its border, and the gradient working spinner;
  • every Button prop except variant (there is only one look): label, size, displayType, iconName, isLoading, isWorking, disableWhenWorking, isFullWidth, tally, statusDot, tooltipText, disabled, isSplitButton and the rest;
  • isAnimated shimmers the border (moved over from the Button proposal). The offset ring (hasOffset) was dropped on 2026-10-21.

It uses the Button's markup and CSS (pds-button, pds-button--secondary), so it matches the regular button's sizes and states. The Button proposal goes back to the plain PDS Button.

Out of scope for now

Other looks (a filled or primary agentic button), the agentic treatment on the other Button variants, and a gradient on the hover and active states beyond what the secondary button does.

Source

The designer's decision in design review on 2026-10-21. No Figma or Jira.