phowell
/
pocketflow
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add agent diagram

This commit is contained in:
zachary62 2025-03-05 15:39:45 -05:00
parent 5855a377e2
commit 3f9a5bc368
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
assets/agent.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 65 KiB

4
docs/design_pattern/agent.md
View File

@ -10,6 +10,10 @@ nav_order: 6
Agent is a powerful design pattern, where node can take dynamic actions based on the context it receives. Agent is a powerful design pattern, where node can take dynamic actions based on the context it receives.
To express an agent, create a Node (the agent) with [branching](../core_abstraction/flow.md) to other nodes (Actions). To express an agent, create a Node (the agent) with [branching](../core_abstraction/flow.md) to other nodes (Actions).
<div align="center">
<img src="https://github.com/the-pocket/PocketFlow/raw/main/assets/agent.png?raw=true" width="400"/>
</div>
> The core of build **performant** and **reliable** agents boils down to: > The core of build **performant** and **reliable** agents boils down to:
> >
> 1. **Context Management:** Provide *clear, relevant context* so agents can understand the problem.E.g., Rather than dumping an entire chat history or entire files, use a [Workflow](./workflow.md) that filters out and includes only the most relevant information. > 1. **Context Management:** Provide *clear, relevant context* so agents can understand the problem.E.g., Rather than dumping an entire chat history or entire files, use a [Workflow](./workflow.md) that filters out and includes only the most relevant information.