Chris Reddington, Developer Advocate Developer Advocate.

With the plan approved, ToolSmith starts building, and the first thing it needs is a connection to PurpleSuite. The sixth video in the Build EmployeeWorks plugins with ToolSmith series enters the API key and instance ID in a secure configuration form (never in chat), follows a failed test through to an updated plan, then checks what ToolSmith created against that plan.

A static Astro website for a South Wales carpentry and construction business, built with no CMS, database, or client-side framework, and deployed to GitHub Pages on a custom domain.

One model reviewing its own plan tends to agree with itself. So I built a cleanup workflow shaped like a jury: separate critics from a deliberate mix of model families weigh the evidence, with a simple forcing function that keeps neighbouring reviewers off the same family. The orchestrator presides as judge, refuting rather than merging, votes promote shared findings, and a post-approval diff check can overrule a verdict that was unanimous and still wrong.

Building with one agent is familiar. Orchestrating a fleet of them in parallel across local, background, and cloud surfaces is where it gets real. This session covers the decisions that matter, how to decompose work across agents, when to fork vs. delegate, and how to verify quality when agents outnumber you — with patterns for multi-agent workflows you can apply to your own codebase.

An interactive mental model for agentic AI that explains how instructions, retrieved context, session state, memory, MCP servers, sandbox execution, tool results, and the Think-Act-Observe loop fit together.

Conversation state and retrieved context lead naturally into memory, but only if we're clear about what memory is for. Rules, skills, and instruction files package what you already know. Memory should capture what the work itself teaches the system, and that means reflection, verification, and forgetting matter just as much as recall.