Skip to content
KiweelyKiweelyKiweely

Codex with wdcli: Validate, Deploy, and Stop at Development

Codex can run shell commands like wdcli in a repo. Gate it to Development tenant deploys only; keep promotions on a human path.

  • By Kiweely
  • Updated
  • 1 min read
On this page

OpenAI’s Codex CLI can inspect repos and run commands. Workday’s WDCLI manages Extend apps from the terminal. Together they are useful—and dangerous if promotions are in scope.

Safe loop

  1. Codex edits local Extend sources.
  2. Run validate (App Builder Validate or project-equivalent via WDCLI as your install supports).
  3. Deploy only to a named Development tenant.
  4. Human runs persona tests (Start Proxy in non-Production).
  5. Humans own Implementation/Sandbox/Production promotion.

Hard stops to encode in instructions

  • No Production deploy commands.
  • No App Hub promotion without explicit human approval text.
  • No personal API keys for client repos.
  • Log every wdcli command in the PR/work notes.

Workday’s Developer Agent install docs list Claude Code, Cursor, VS Code, and Antigravity—not a first-party Codex installer. Codex remains a general agent driving your WDCLI, not a Workday-branded substitute for Developer Agent skills.

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.

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.

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