Skip to content
KiweelyKiweelyKiweely

Install Workday Developer Agent in Claude Code, Cursor, or VS Code

Developer Agent needs WDCLI plus the IDE extension. Workday lists Claude Code, Cursor, VS Code, and Google Antigravity. Sign in with developer credentials before you build.

  • Checked against Workday on
  • Applies to Workday Extend
  • 2 min read
  • Published
  • By Kiweely
On this page

Workday documents a concrete install path for Developer Agent inside the coding tools many Extend developers already use. This guide restates those steps without inventing extra product features.

Prerequisites Workday lists

From Install and Configure Developer Agent Extension on an IDE:

  • One of these IDEs: Claude Code, Cursor, VS Code, or Google Antigravity
  • An Extend account with access to your Workday tenant

Workday states that the Developer Agent Extension requires both the WDCLI app and the IDE extension.

Steps Workday documents

  1. Open the Developer Agent page on the Developer Site.
  2. Install the Workday CLI (WDCLI). Workday says WDCLI manages Extend apps, deploys code, and interacts with the Workday Build Platform from the terminal.
  3. Download the latest WDCLI from the Developer Site, run the installer for your machine, then authenticate with wdcli auth login and complete the browser sign-in with your developer credentials.
  4. Select the button for your IDE.
  5. Select the Developer Agent download button.
  6. Follow the install instructions shown for that IDE.

Workday’s Developer Agent product page adds that you can also use Developer Agent from the Developer Site itself, and that it is generally available starting 2026R2+ only through Extend AI, with Flex Credits-based pricing.

Claude Code–specific notes from Workday’s GitHub repo

Workday publishes WorkdayDeveloperAgentForClaude. That repository states:

  • The plugin is designed for the Claude Code CLI experience and is currently not enabled in other Claude surfaces.
  • Setup expects WDCLI signed in, the Developer Agent extension signed in for VS Code or Cursor as documented there, and the Claude Code plugin installed from the marketplace (or a local plugin directory for development).
  • Open an Extend project and ask for the change; Claude delegates to Developer Agent, and you review and approve in the panel.

If your install fails, Workday’s repo documents a /dev-agent-doctor command that checks WDCLI install, connector support, and sign-in.

After install: what to verify

  1. wdcli responds and you are signed in as the intended developer identity.
  2. The IDE shows Developer Agent available for the open Extend project.
  3. A trivial ask (for example, explain one component) completes, then check invocation usage—Workday documents that every interaction uses at least one invocation and that code generation can use several hundred.

Limits

This guide does not replace the live Developer Site download page. Screens and button labels can change; follow the page you see after sign-in. Confirm entitlement with the customer’s Workday account team before using Developer Agent on a company tenant.

Sources checked

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.