---
title: "Fix Workday Developer Agent VS Code Personal Login & Errors"
description: "How to fix VS Code Workday Developer Agent sign-in timeouts on personal accounts using wdcli auth login --environment personal, and resolve HITL interrupt…"
url: https://kiweely.com/guides/workday-developer-agent-vscode-personal-account-login
---

# Fixing Workday Developer Agent VS Code Sign-In With a Personal Developer Account and Subagent Interrupt Errors

Clicking Sign In inside the VS Code Workday Developer Agent extension routes through the non-personal authentication flow and times out for personal Workday Digital ID accounts. Authenticate via wdcli auth login --environment personal in your terminal, reload VS Code, and update the extension.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   4 min read
-   Published November 6
-   By Kiweely

## Why the VS Code Developer Agent Sign-In button times out on personal accounts

The **Workday Development Tools** extension for VS Code (which hosts the **Workday Developer Agent**) requires both the IDE extension and the **Workday Developer CLI (`wdcli`)** installed on your workstation. When you click the **Sign In** button directly inside the VS Code Developer Agent extension sidebar, the extension launches the default enterprise developer site authentication flow (`wdcli auth login` without environment flags).

If you use a **personal developer account** ([Open Developer Program](https://kiweely.com/guides/workday-open-developer-program-getting-started)) authenticated through **Workday Digital ID**, completing the browser login launched by the extension’s **Sign In** button finishes in the browser tab but never hands a valid session back to VS Code, causing the extension sign-in request to time out.

## Authenticating via `wdcli auth login --environment personal`

Because the Workday Developer Agent IDE extension reads the local `wdcli` session store on activation, you can bypass the extension’s **Sign In** button entirely and authenticate from your terminal using the `--environment personal` flag:

### 1\. Log in from your terminal with `--environment personal`

Open your terminal and run:

bash

```
wdcli auth login --environment personal
```

Complete the Workday Digital ID sign-in prompt in your browser. Once the browser confirms authentication, verify that the CLI stored your session and active company:

bash

```
wdcli whoami
wdcli account list
```

`wdcli whoami` should exit `0` and print your authenticated user and primary company. If you belong to multiple companies on the Developer Site, switch to the target company with `wdcli account switch` or set `wdcli config set defaultCompanyShortId <companyShortId>`.

### 2\. Reload the VS Code window without clicking Sign In

Do **not** click the **Sign In** button inside the Developer Agent extension panel, as that will overwrite or restart the non-personal login flow. Instead:

1.  Open the VS Code Command Palette (`Cmd+Shift+P` on macOS or `Ctrl+Shift+P` on Windows/Linux).
2.  Run **Developer: Reload Window**.
3.  When the extension activates on reload, it reads the stored `wdcli` credential from disk and brings up the Developer Agent chat in an authenticated state automatically.

### 3\. Fix `PATH` mismatches and session expiry

Two environment issues can prevent VS Code from picking up your `wdcli` login:

-   **GUI-launched VS Code missing `wdcli` on `PATH`:** If the Developer Agent sidebar still shows signed out after running **Developer: Reload Window**, quit VS Code and launch it (`code .`) directly from the same terminal shell where `wdcli whoami` succeeded. A macOS Dock or Windows Start Menu launch often inherits a minimal system `PATH` that cannot locate the `wdcli` binary or its configuration directory.
-   **Session timeout after several hours:** Personal `wdcli` sessions expire after a few hours. When the Developer Agent chat reports `Authentication required`, re-run `wdcli auth login --environment personal` in your terminal and run **Developer: Reload Window** again.
-   **Tenanted code generation:** When prompting Developer Agent to generate Graph API queries/mutations for deployed Model Business Objects, WQL queries, or `.agentskill` files with tenant-specific Agent-Ready Tools, also authenticate to your target tenant (`wdcli tenant login <tenant-alias>`) so the agent can inspect your tenant metadata. If the tenant itself won’t sign in, see [why your personal Workday developer tenant won’t open or sign in](https://kiweely.com/guides/workday-developer-tenant-sign-in-problems).

## Fixing `HITL interrupt misalignment` when Developer Agent invokes subagents

When prompting the Developer Agent in VS Code to scaffold multi-component apps or create Custom Agents (which delegates work to internal subagents such as the Custom Agent Creator subagent), older IDE and extension builds frequently fail mid-turn with:

text

```
Developer Agent ran into an issue: 'HITL interrupt misalignment: 1 action request(s) but 0 gated tool call(s) on the triggering message — the gated set must match the graph's interrupt on config.' Try again or rephrase your request.
```

This error occurs when the human-in-the-loop (HITL) tool-approval graph on the Developer Agent backend expects a gated tool-call confirmation structure that an older VS Code client or outdated **Workday Development Tools** extension version does not serialize properly.

To resolve the `HITL interrupt misalignment` error:

1.  Update **VS Code** itself to the current stable release (**Code** > **Check for Updates...** or **Help** > **Check for Updates...**).
2.  In the VS Code **Extensions** view (`Cmd+Shift+X` / `Ctrl+Shift+X`), search for **Workday Development Tools** (and the Developer Agent extension downloaded from `https://developer.workday.com/developer-agent`) and update it to the latest version, and update `wdcli` (`wdcli version`).
3.  Reload the window (**Developer: Reload Window**) and start a **new** Developer Agent chat session rather than resuming the broken session whose conversation history still holds the misaligned interrupt state. You can also toggle auto-approval in the Developer Agent toolbar settings if you want subagent file edits applied without per-step confirmation prompts.

## Verifying the setup in VS Code and your tenant

In your terminal, confirm `wdcli whoami` and `wdcli tenant list` return your account and connected Development tenant. Reload VS Code, open the **Developer Agent** panel, and send a prompt that invokes a subagent and tenant metadata lookup (such as asking it to generate a `.agentskill` file or a WQL query for your app). Confirm that the subagent completes without throwing `HITL interrupt misalignment` and proposes the generated files in your workspace diff view.

## Sources checked

-   [Install and Configure Developer Agent Extension on an IDE](https://developer.workday.com/documentation/GUID-d278400c-de70-4c66-aca8-aaf33db7dc96-enHYPHENus)
-   [Developer Agent Overview](https://developer.workday.com/documentation/GUID-f1ddebc6-077a-4441-a023-3c857db88053-enHYPHENus)
-   [Things to Consider When Using Developer Agent](https://developer.workday.com/documentation/GUID-fc7bcf73-9df8-43fe-919d-081de5abb511-enHYPHENus)
-   [Chat with Developer Agent](https://developer.workday.com/documentation/GUID-d068255a-572e-4988-9539-814c090a7242-enHYPHENus)
-   [Reference: Workday Developer CLI (WDCLI) for Extend Apps Commands](https://developer.workday.com/documentation/GUID-16d9d3f3-ba63-4022-8a84-ad78bd5189ca-enHYPHENus)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Why a Workday Custom Agent Has No Credentials Tab in Agent Management Hub, and How to Expose It Through A2A Workday displays the Credentials tab in Agent Management Hub only for registered External Agents. To expose a Custom Agent built on Workday’s AI platform to an external assistant, register a third-party Agent Definition in the Agent System of Record that wraps the Custom Agent WID as an A2A tool.](https://kiweely.com/guides/workday-custom-agent-missing-credentials-tab-a2a)
-   [### Preventing Duplicate Initiate\_Change\_Job Business Process Events When a Workday Custom Agent Calls a Write Tool When a Custom Agent write tool calls Initiate\_Change\_Job without returning a clear Change Job business process WID in its response payload, the LLM assumes the call did not produce a WID and retries. Return the explicit event WID, set Destructive annotations, and check for in-progress events.](https://kiweely.com/guides/workday-custom-agent-duplicate-initiate-change-job)
-   [### Why Custom Agent Actions Fail With S22 Permission Denied or Task Not Authorized in Agent Chat Orchestration Builder runs Custom Agent Actions directly as your user, whereas Agent Chat enforces dual ASOR authorization and restricts the Agent System User token to the resources listed in your .agentskill file. Register every REST, SOAP, and WQL resource WID via the Finder API to fix it.](https://kiweely.com/guides/workday-custom-agent-actions-permission-denied-tool-wids)
-   [### Why Custom Agent Skills Deployed From the Developer Site Don’t Appear in Agent Management Hub, and ASOR Tenant Prerequisites When you deploy a Custom Agent with multiple .agentskill files from App Builder, Workday’s Agent System of Record packages all of their tools into a single combined skill registration that starts disabled. Learn how to enable and sync skills in Agent Management Hub and verify ASOR prerequisites.](https://kiweely.com/guides/workday-agent-management-hub-skills-not-showing)
-   [### Why won’t my personal Workday Extend developer tenant sign in or open, and how do I move my apps if it expires? Check Console > Tenants first. A personal tenant with no activity for 7 days is deleted; otherwise reset the password, sign in as lmcneil, and wait out weekly maintenance. If it is gone, request a new tenant and redeploy from App Hub.](https://kiweely.com/guides/workday-developer-tenant-sign-in-problems)
-   [### What is the difference between a Workday personal developer account and a company Workday Extend account? A personal account is free, belongs to one person and holds one development tenant that is deleted after 7 idle days. A company account belongs to an Extend customer, follows its contract and can promote apps to Production.](https://kiweely.com/guides/workday-personal-vs-company-developer-account)
-   [### How to get a Workday developer account and a free development tenant Create a free account at developer.workday.com, open Console > Tenants, request a development tenant, then sign in as lmcneil with the emailed password and change it within 72 hours. Sign in at least every 7 days or the tenant is deleted.](https://kiweely.com/guides/workday-open-developer-program-getting-started)

### More guides on Custom agents and Workday AI

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

-   [Finding Workday tool IDs with the Agent Resource Search (finder) API](https://kiweely.com/guides/workday-finder-api-tool-discovery)
-   [Connecting an Extend app to the Workday Self-Service Agent and Microsoft Teams](https://kiweely.com/guides/workday-extend-self-service-agent-teams)
-   [How to build a chatbot in Workday Extend](https://kiweely.com/guides/workday-extend-chatbot)
-   [How to call AI Gateway Document Intelligence from a Workday Extend app](https://kiweely.com/guides/workday-extend-ai-gateway-document-intelligence)
-   [Who gets Workday Developer Agent, and what it uses in Flex Credits](https://kiweely.com/guides/workday-developer-agent-access-flex-credits)
-   [Connecting a Workday custom agent to an outside agent platform with A2A](https://kiweely.com/guides/workday-custom-agents-a2a-external-agents)
-   [Why Workday custom agents use up Flex Credits so quickly](https://kiweely.com/guides/workday-custom-agent-usage-limits)
-   [A Workday custom agent’s lifecycle, from first deploy to Production](https://kiweely.com/guides/workday-custom-agent-lifecycle-promotion)

### From the blog on Custom agents and Workday AI

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

-   [Migrating a Workday Extend App from Hand-Edited JSON to an Agent-Maintained Repo](https://kiweely.com/blog/migrate-extend-app-to-agent-maintained-repo)
-   [Staffing a Workday AI Rollout: FDE, HRIS Admin, Security, and the Agent](https://kiweely.com/blog/staffing-workday-ai-rollout-fde-hris-security)
-   [From Click-Path Trainer to Agent Supervisor: A 90-Day Upskill Path](https://kiweely.com/blog/from-click-path-trainer-to-agent-supervisor-90-days)

## Let Workday check the work.

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

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

## Get the next guide in your inbox.

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