--- title: 'Loop Engineering named the shift: the prompt is no longer the unit of work.' publication: Agent Techniques Weekly slug: 2026-W25 issueNumber: 9 isoYear: 2026 isoWeek: 25 cadence: weekly publishedAt: '2026-06-20' periodLabel: Week 25 of 2026 canonicalUrl: https://brianletort.ai/industry/agents/2026-W25 schemaVersion: 2026.05.02 technique: name: Loop Engineering mode: automate agentCapabilities: - vendor: OpenAI product: Codex mode: build date: '2026-06-20' - vendor: Anthropic product: Claude / Claude Code mode: cowork date: '2026-06-20' - vendor: Microsoft product: Copilot / Scout mode: automate date: '2026-06-20' skillsAndConnectors: - ecosystem: MCP-capable agents name: Connector-backed workflow type: connector date: '2026-06-20' - ecosystem: Claude / Cursor / Codex / Hermes name: Reusable skills type: skill date: '2026-06-20' proofOfValue: - actor: Practitioner teams workflow: Coding, research, operations, and professional drafting evidence: vendor_claim scorecardAsOf: '2026-06-20' --- # Loop Engineering named the shift: the prompt is no longer the unit of work. *Agent Techniques Weekly · Issue 09 · Week 25 of 2026 · Published 2026-06-20* ## Big Read W25's launch issue puts a name on the operating shift. Loop Engineering means designing the cycle that wakes an agent, supplies context, lets it act, checks the result, retries or escalates, stores state, and knows when to stop. That is the move from using AI in a chat window to managing AI as a bounded coworker, builder, and background automation system. ## Technique of the Week ### Loop Engineering Mode: `automate`. Design the trigger-context-action-verification-state-stop cycle around the agent instead of hand-prompting every next step. **Why it matters.** Loop Engineering moves the human up a level: from operator to system designer. The hard part becomes the loop contract and verifier, not the prose of the initial prompt. **Anatomy:** - **Goal.** State the outcome and the boundary of delegated work. - **Context.** Give the agent the sources, files, examples, and constraints it needs. - **Tools.** Limit actions to the connectors, commands, and systems required for the job. - **Verifier.** Define how the output is checked before it is trusted. - **Escalation.** Name what requires human review, approval, or rollback. **Where it shows up:** - Codex automations - Claude/Cursor coding loops - Microsoft Scout - Hermes recurring workflows Source: [Addy Osmani, Loop Engineering](https://addyo.substack.com/p/loop-engineering). ## New Agent Capabilities ### OpenAI — Codex Mode: `build`. Date: 2026-06-20. **Capability.** Workspace-bound coding assistance increasingly organized around issues, tests, review, and automation hooks. **Read.** The durable read is not any single coding model; it is the emergence of a build harness where context, tools, and verification are part of the workflow. Source: [Introducing the Codex app](https://openai.com/index/introducing-the-codex-app/). ### Anthropic — Claude / Claude Code Mode: `cowork`. Date: 2026-06-20. **Capability.** Persistent instructions, skills, and agentic coding workflows point toward reusable professional work patterns. **Read.** Claude-style workflows are strongest when the human supplies policy, examples, and review criteria that survive beyond one chat. Source: [Loop Engineering, O'Reilly Radar](https://www.oreilly.com/radar/loop-engineering/). ### Microsoft — Copilot / Scout Mode: `automate`. Date: 2026-06-20. **Capability.** The Microsoft agent surface is moving toward M365-grounded action, background coordination, and enterprise controls. **Read.** The enterprise differentiator is governed access to mail, calendar, files, identity, and policy, not generic answer quality. Source: [Introducing the Codex app](https://openai.com/index/introducing-the-codex-app/). ## New Skills and Connectors ### MCP-capable agents — Connector-backed workflow Type: `connector`. Date: 2026-06-20. **Signal.** Agents increasingly use connectors to reach source systems instead of relying on pasted context. **Why it matters.** Connectors turn chat into work by letting agents read the system of record and return traceable output. Source: [Loop Engineering, O'Reilly Radar](https://www.oreilly.com/radar/loop-engineering/). ### Claude / Cursor / Codex / Hermes — Reusable skills Type: `skill`. Date: 2026-06-20. **Signal.** Repeated workflows are being packaged as skills, rules, plugins, and templates. **Why it matters.** Skills are the portability layer for operating knowledge; they prevent teams from re-teaching the same workflow every week. Source: [Loop Engineering, O'Reilly Radar](https://www.oreilly.com/radar/loop-engineering/). ## Proof of Value ### Practitioner teams — Coding, research, operations, and professional drafting Evidence quality: `vendor_claim`. **Claim.** The strongest reported wins come from bounded workflows with clear checks, not open-ended autonomy. **Read.** Treat value claims as credible when the workflow, baseline, and verifier are visible. Treat broad percentage claims without methods as directional at best. Source: [OpenAI Codex app announcement](https://openai.com/index/introducing-the-codex-app/). ## Enterprise Readiness - **permissioning.** Agents need least-privilege access scoped to the workflow, not broad user-equivalent authority by default. - **verification.** Every higher-autonomy workflow needs a deterministic check, source trail, rubric review, or human approval gate. - **auditability.** Background agents should produce inspectable logs of prompts, tool calls, approvals, outputs, and state changes. - **cost.** Loops need budgets and stop conditions because repeated agent calls can turn productivity experiments into runaway spend. ## Scorecard As of 2026-06-20. | Mode | Leading pattern | Representative tools | Control gap | |---|---|---|---| | chat | Structured context and critique loops | ChatGPT, Claude, Copilot Chat | Quality still depends on the user's review discipline. | | cowork | Human-supervised delegation with persistent project memory | Claude Cowork, Microsoft Copilot, Cursor | State, approvals, and source grounding must be visible. | | build | Workspace-bound agents with tools, tests, and worktrees | Claude Code, Codex, Cursor, OpenCode | Verification quality determines whether speed becomes rework. | | automate | Scheduled loops with state, tools, and escalation gates | Codex Automations, Microsoft Scout, Hermes, OpenClaw | Always-on agents need identity, audit trails, budgets, and stop conditions. | ## Try This ### Run a Loop Engineering experiment 1. Pick one recurring weekly task with a clear definition of done. 2. Write a one-page loop contract: goal, context, tools, verifier, stop condition, and escalation rule. 3. Run it manually once with an agent and record where the verifier was weak. 4. Only automate the task after the verifier catches the most likely failure mode. **Expected outcome.** A reusable workflow contract and a clearer read on whether the task is ready for cowork, build, or automate mode. ## Watchlist - **Next 7 days — Copilot and Scout agent releases.** Microsoft's advantage is governed enterprise context; any new background or M365 action capability changes the automation surface. - **Next 7 days — Claude and Codex skill ecosystems.** Reusable skills and plugins are the leading indicator that agentic workflows are becoming products, not prompts. - **Next 30 days — Hermes, OpenClaw, OpenCode, and adjacent OSS harnesses.** Open-source harnesses reveal which control points matter most: memory, channels, terminal build loops, or automations. - **Next 30 days — Evidence-backed value claims.** The newsletter should elevate wins with named workflows, baselines, and verification methods, not generic productivity claims. ## Changelog - Backfilled Agent Techniques Weekly issue 09 for Week 25 of 2026. --- Source of truth: `src/data/industry/agents/2026-W25.ts`. Canonical HTML: .