Build an AI Agent (From Scratch)

Facts 10 chapters$29.29 (at the time of this writing)315 pages Chapters Building your first LLM agentWhat is an AI agent?

Disclaimer

This post includes affiliate links; I may receive compensation if you purchase the book from the different links provided in this post.

This review is about Build an AI Agent (From Scratch) by Jungjun Hur and Younghee Song from Manning.

Facts

  • 10 chapters
  • $29.29 (at the time of this writing)
  • 315 pages

Chapters

  1. Building your first LLM agent
    1. What is an AI agent?
    2. The brain of AI agents: LLMs
    3. Enabling actions: Tool use
    4. Implementing a basic ReAct agent
  2. Developing advanced agent capabilities
    1. Building knowledge bases with RAG
    2. Adding memory to your agent
    3. Planning and reflection for complex tasks
    4. Empowering agents with code execution
    5. Orchestrating multi-agent systems
    6. Evaluating agents

Pros and cons

At Manning, I consider the following two books to be references:

  • Kubernetes in Action by Marko Lukša. It’s the book that taught me the foundations of Kubernetes. Fun fact: I got it from the author at a conference in exchange for Swiss chocolate.
  • API Design Patterns. I read it while working on the Apache APISIX API gateway. At this time, I was deeply involved in (RESTful) APIs. I had read a lot on APIs; I had researched a lot; I held talks on APIs; I talked with lots of people about APIs. And yet, the book was a revelation, full of brilliant insights.

I think that Build an AI Agent is as fundamental to me as the other two were.

While there are few chances that you will actually build an AI agent, this book teaches you the basics (and more) of how they operate. It starts with the agent loop, then proceeds to tools, then to MCP, etc.

The only thing I would like to see for the next edition is for the developers to beef up the evaluating agents part.

Conclusion

If you use AI agents and want to understand what happens when you use them, this is the book for you. I think it should belong in the library of any engineer worthy of the name.