---
title: "App Builder vs Claude Code for Workday Developer Agent"
description: "Developer Agent in App Builder and Developer Agent in Claude Code are the same assistant and the same invocation meter. The IDE adds the CLI and the extension."
url: https://kiweely.com/blog/app-builder-vs-claude-code-developer-agent
---

# App Builder vs Claude Code for Workday Developer Agent

Workday documents Developer Agent inside App Builder and, with the Workday CLI plus the Developer Agent extension, inside Claude Code and other editors. Both count toward the same entitlement. The IDE does not configure tenant security, and it does not change the weekly model-component update.

-   By Kiweely
-   November 16
-   Updated November 19
-   6 min read

App Builder and Claude Code are two places Workday lets you talk to Developer Agent. They are not two products with two meters. The [overview](https://developer.workday.com/documentation/GUID-f1ddebc6-077a-4441-a023-3c857db88053-enHYPHENus/DeveloperAgentOverview) says you can use Developer Agent directly in App Builder, or through the Developer Agent extension plus the Workday command-line interface in Claude Code and in any VS Code-compatible editor. The examples it names are VS Code, Cursor, and Windsurf. The install page’s prerequisite list is Claude Code, Cursor, VS Code, and Google Antigravity. The marketing page adds the same set and says you can also work from the Workday Developer Site.

The entitlements page is the line that should settle the budget argument: every Developer Agent use on the Developer Site or in a desktop IDE counts toward the entitlement, and Workday meters the chat interface and the plugin or connector at the same rate.

## What each place actually is

**App Builder** is the browser tool on the Developer Site. You create an app, connect a development tenant, and type into “What do you want to build?” or the chat icon. The nomination tutorial lives entirely here. You see added components in green and updated ones in yellow, you open App Preview, and you choose Apply Changes or Reject Changes. Save to App Hub and Save and Deploy are buttons in the same window. Validate is in that window too. This is the shortest path from a prompt to a development tenant, because the app is already in App Hub’s session.

**Claude Code, and the other listed editors,** require two installs. The install page says the extension needs both the Workday CLI and the extension.

1.  Open the Developer Agent page on the Developer Site.
2.  Install the Workday CLI. Workday says it manages Extend apps, deploys code, and talks to the Workday Build platform from a terminal. Download it from the Developer Site and run the installer.
3.  Authenticate with `wdcli auth login` and complete the browser sign-in. The extension shares that CLI session, so this login is the login for both.
4.  Choose the button for your editor and install the Developer Agent extension from the download instructions on that page.

You need an Extend account with access to your Workday tenant. The install page does not say a personal Build tutorial account is sufficient for the extension, and it does not say it is insufficient. The marketing page says Developer Agent is generally available starting 2026R2+, with Flex Credits-based pricing, and Workday’s Developer Agent datasheet says it is available only through Extend AI. If the extension will not sign in, that access gap is the published place to look. Do not keep reinstalling the extension as if it were a local defect.

A separate getting-started note for the integration CLI prints `wdcli auth:login` with a colon. The Developer Agent install page prints `wdcli auth login` with a space. Use the command on the page for the tool you just installed. Those pages were both live on November 16, 2026, and they do not match.

## What does not change when you switch windows

| Question | App Builder | Claude Code with the extension |
| --- | --- | --- |
| Which assistant | Developer Agent | Developer Agent |
| What an invocation costs | One query or command, same entitlement | Same |
| Can it scaffold business objects, PMDs, scripts, WQL, and Graph queries | Yes, per the overview | The overview describes the agent, not a separate IDE skill list |
| Does it configure tenant security | No. You do that after deploy | No. The overview says the same sentence once, for the agent |
| Does it register an agent for governance | It can write a skill file listing tools so you can register with the Agent System of Record | Same agent |
| Weekly model-component update | Unchanged. The IDE does not promote around Friday | Unchanged |
| Where the app version lives | App Hub when you save | App Hub when you upload or deploy with the CLI |

The marketing page describes the split with general-purpose editors in one paragraph. Cursor and Claude Code, used on their own, do not know Workday’s data model, business processes, or logic. Developer Agent is the layer Workday says has that domain knowledge, and the marketing page says it plugs into those tools via MCP. Turning on Claude Code without the extension is the general-purpose case. Installing the extension is how Workday says you get Developer Agent inside that editor. The extension does not turn Claude Code into App Builder. You still need the CLI to deploy, and you still need a tenant connection and a security policy.

Workday says the agent can create a skill file, YAML or JSON, listing the tools an agent uses, to help registration with the Agent System of Record. It says the agent does not configure security. After deploy, security is a tenant task. That is true whether the skill file was written from a browser chat or from Claude Code.

## When the browser is the better window

Use App Builder when you are learning the nomination tutorial, when you need App Preview against a connected tenant, or when you want Validate, the build log, and Deploy to Tenant in the same place as the diff. The tutorial’s proof is visual: green and yellow files, a preview that searches for a worker, App Manager’s instance count. An editor can show you JSON. It does not replace that preview unless you run the CLI preview command on purpose.

`wdcli app preview` opens a local preview and is available for Extend apps only. If you use local disk sync, the CLI and the sync folder have to be the same folder or the preview is wrong. That is a foot-gun the browser session does not have, because the browser session is the App Hub session until you save.

## When the editor is the better window

Use the extension when the app is already on disk and you are reviewing a pull request, or when you want the CLI’s `validate`, `upload`, `deploy`, and `promote` next to the files. Promote from the CLI follows the same levels and the same model-component deadlines as the Developer Site. The editor does not get a faster Friday.

Also use the editor when more than one person must see the diff before Apply. App Builder’s Discard Changes destroys the session irreversibly and leaves App Hub where it was. A git commit of a local-disk-sync folder is a review point the browser session does not give you. The agent can still spend invocations while you stare at the diff. The meter does not pause for code review.

## A trap in both places

People run a long correction loop in Claude Code because it feels like a local tool, then open App Builder and run the same loop again because they do not trust that the extension saved. Both loops are invocations. Save or upload once, then look at App Hub. `wdcli app info` and `wdcli app versions` tell you what the hub has. Guessing from the editor buffer does not.

The other trap is security. A beautiful PMD in Claude Code can deploy and still do nothing for HR Administrator, because nobody activated the domain security policy. The browser tutorial forces that step. The IDE install page never mentions it. Bring the tenant step with you.

## Frequently asked questions

### Does Claude Code include Developer Agent without the extension?

Not according to Workday. The install page says the extension requires the Workday CLI and the extension. The marketing page says general-purpose Claude Code has no knowledge of Workday’s data model. The extension is the published bridge.

### Are IDE prompts cheaper than App Builder prompts?

No. The entitlements page says they are metered at the same rate and count toward the same entitlement.

### Can I deploy to Production from Claude Code?

You can run the CLI promote command. It follows the same rules as the Developer Site: one level at a time, a Production checklist, and the weekly service update for model components. The editor is not a second promotion pipeline.

### Which login command is correct?

The Developer Agent install page shows `wdcli auth login`. A different CLI getting-started page shows `wdcli auth:login`. Run the command printed on the page you used to install, and complete the browser sign-in it opens.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 16 ### What to put in a Workday SOW when agents are in scope](https://kiweely.com/blog/workday-implementation-sow-ai-agents)
-   [November 16 ### Can AI agents speed up a Workday implementation? What they do in the tenant today](https://kiweely.com/blog/kiweely-vine-workday-implementation-project)
-   [November 16 ### A hybrid Workday build: people, Deployment Agent, and a desktop agent](https://kiweely.com/blog/hybrid-workday-delivery-ai-agents)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [How to Use an AI Agent for Workday Testing (Step-by-Step Guide)](https://kiweely.com/guides/how-to-use-ai-agent-for-workday-testing)
-   [Workday Implementation Phases: Workday’s Own Stages, and What Stays Manual vs What an AI Agent Does](https://kiweely.com/guides/workday-implementation-phases)
-   [Deployment Agent Users domain and View Security for Agent Skill](https://kiweely.com/guides/workday-deployment-agent-users-domain-security)
-   [Deployment Agent prompt patterns: in my tenant and CRAFT](https://kiweely.com/guides/workday-deployment-agent-prompt-patterns)
-   [Deployment Agent Configuration Catalog Support for Implementers](https://kiweely.com/guides/deployment-agent-configuration-catalog)
-   [Workday Custom Agent First POC Checklist for Implementers](https://kiweely.com/guides/workday-custom-agent-first-poc-checklist)
-   [Workday Developer Agent and Agent-Ready Tools for Implementers](https://kiweely.com/guides/workday-developer-agent-and-agent-ready-tools)
-   [Workday First-Party Agent Tenant Prerequisites for Implementers](https://kiweely.com/guides/workday-first-party-agent-tenant-prerequisites)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
