← Table of Contents · Page 518 of 868

SURVEY OF AGENT FRAMEWORKS

Part 11 of 11

CHECK YOUR UNDERSTANDING • Why are graphs a good fit for agents? ◦ Answer: Agents need loops and shared state, and graphs express cycles, branching, and carried state explicitly. • What is the main risk of a crew-style framework? ◦ Answer: Hidden hand-offs and framework-added prompt text can make it hard to see why an agent behaved as it did, and extra agents add cost. • Who benefits most from a minimal framework? ◦ Answer: Teams who want maximum control and little hidden behavior, and who are willing to build memory, safety, and verification themselves. • Name two reasons to build your own harness instead of adopting a framework. ◦ Answer: Unusual requirements that a general framework fights against, and a wish to understand every piece for debugging and safety. • How can you reduce the risk of lock-in to a framework? ◦ Answer: Wrap the framework in a thin layer of your own code, so only that layer changes if you switch.
Advertisement
Read Aloud:
0:00 / 0:00