The Built-in Agent Toolkit (2026)

WorkDaddy agents don’t just chat — they execute. 17 built-in tools cover the full loop: real shell commands, surgical file edits, live browser checks, web research, creative production, and human-approval gates.

Under every WorkDaddy agent is the same engine that powers serious coding agents — extended for commerce. This page documents the 17 built-in tools that ship with the app in 2026: what each does, why it matters for an e-commerce team, and how the draft-first policy keeps every powerful capability accountable. If MCP servers and connectors are what agents reach out to, these tools are what agents are.

The toolkit, by layer

The tools compose into a working loop — find, change, verify, ship:

  • Core coding: bash shell, file read/write/edit/patch, glob & grep search, language-server navigation, repository tools

  • Research: live web search (Exa / Parallel) and full-page web fetch

  • Orchestration: background subagents, structured todo plans, reusable skills, human-approval gates

  • Automation: a real browser panel, an interactive PTY terminal, and cron-style scheduled tasks

  • Creative & interface: image generation, native Word/Excel/PowerPoint output, and hands-free voice mode

Why built-in beats bolted-on in 2026

Because the tools share one workspace and one approval policy, agents chain them without glue code: search finds the file, LSP traces the usage, edit changes it, the browser verifies the storefront, and the scheduler makes it recur. Every step is logged and reviewable — which is exactly what you want when the workspace is your revenue.

Frequently asked questions

What tools do WorkDaddy agents have in 2026?

All 17 built-in tools: bash, file editing, code search, LSP, web fetch, web search, subagents, todo planning, skills, approval gates, browser automation, image generation, Office document output, an interactive terminal, scheduled tasks, voice mode, and repository tools.

Can WorkDaddy agents really run code and commands?

Yes — agents execute real shell commands and edit real files in a sandboxed workspace. Irreversible operations are approval-gated, and every change is presented as a reviewable diff.

How do built-in tools differ from MCP integrations?

Built-in tools are the agent’s own hands — local execution, editing, browsing, and research. MCP servers and connectors are the outside world: SaaS platforms, data sources, and services. Real work usually chains both.

Do I need to configure anything to use these tools?

No — the toolkit ships with the app. Only a few surfaces need keys (voice mode and image generation use OpenAI APIs) or OS permissions (computer use on macOS).

Put the team to work on your store

Connect your storefront, analytics, and email stack, set a goal, and let the agents run the work end to end. Start on the free plan with your own model key.