liveBook · Manning

Chapter 1: The agent paradigm shift

What you will learn in chapter 1 of Designing AI Agents

The chapter introduction uses a coding-agent failure to explain why model-directed decisions require agent design patterns, while connecting those patterns to established engineering practice.

After this chapter you will be able to

Section by section

Introduction

The chapter introduction uses a coding-agent failure to explain why model-directed decisions require agent design patterns, while connecting those patterns to established engineering practice.

Key terms: working context, rollout utility, Gang of Four patterns, agent design patterns, runtime, probabilistic, opaque, distributed-systems patterns, engineering ancestors, decision-maker

1.1 What exactly is an agent?

This section defines an agent by model-directed control flow, explains how its harness and feedback loop bound that control, and introduces the vocabulary used to describe agent systems.

Key terms: agent, model-directed control flow, model, harness, feedback loop, stopping rule, agent system, cognitive function, pattern, execution topology

1.2 From fixed control flow to model-directed control

This section contrasts fixed software control flow with model-directed agent decisions and explains why engineers must design resource budgets, boundaries, and specifications rather than every branch.

Key terms: fixed control flow, agent loop, model-directed control, bounded resource allocation, harness, context window, task boundary, implementation plateau, design inversion, specification

1.2.1 What breaks and why

The section uses four classical design patterns to show why agent systems move decisions from developer-written control flow to model-directed runtime behavior.

Key terms: GoF, design time, runtime, model, Singleton, working state, volatile context, durable task records, retrieved evidence, Factory

1.2.2 Uncertainties of agent systems

The section explains why agent architectures must account for uncertainty from the start and distinguishes uncertainty in model outputs, agent behavior, and the environment.

Key terms: uncertainty, operating condition, architecture, output uncertainty, non-deterministic outputs, idempotency, behavioral uncertainty, runtime decisions, ReAct agent, environmental uncertainty

1.3 What makes agent patterns fundamentally different

This section explains how agent patterns inherit familiar engineering pressures while changing their implementation because a probabilistic model selects actions at runtime.

Key terms: object-oriented patterns, distributed-systems patterns, agent patterns, probabilistic model, isolation, reconciliation, durable state, budgets, context, tools

1.3.1 What this changes for developers

The section contrasts agent systems with conventional design patterns and identifies the resulting design constraints for developers.

Key terms: GoF, LLM, prompts, typed method signatures, volatile context, durable task records, retrieved evidence, tool outputs, persistence, provenance

1.4 Designing agents through cognitive functions

This section frames agent design as shaping model behavior through engineering choices and introduces cognitive functions as a reference architecture for those choices.

Key terms: models, context, memory, tools, guardrails, evaluation, perception, reasoning, action, reflection

1.4.1 Argus reviews a pull request

Argus’s pull-request review illustrates how seven cognitive functions fit together, while showing why agent engineers must design the harness and specifications that constrain the resulting behavior.

Key terms: Perception, Memory, Reasoning, Action, context triage, attention budget, Reflection, Collaboration, Governance, critic

1.4.2 How this book turns design choices into evidence

The section explains why agent design choices must be judged by their operating tradeoffs and by comparable evidence, not by a pattern name or framework alone.

Key terms: reliability, latency, cost, operational risk, fixed evaluation harness, end-to-end outcomes, defined workload, operating point, benchmark

1.5 Summary

1.6 References

This section lists sources cited in the chapter without explaining new concepts or procedures.

Where this is used later

Concepts explained in this chapter

Chapter 2: Turn a task into an agent architecture →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.