Go to file
zachary62 4a563feb82 design paradigm to design pattern 2025-02-25 18:22:10 -05:00
assets emphasize agent build agent 2025-02-24 09:26:03 -05:00
cookbook update readme 2025-02-23 23:56:23 -05:00
docs design paradigm to design pattern 2025-02-25 18:22:10 -05:00
pocketflow m 2025-02-02 22:30:18 +00:00
tests rename as mini llm flow is poor 2025-01-09 03:01:25 +00:00
.gitignore add examples 2024-12-27 05:29:24 +00:00
LICENSE Create LICENSE 2024-12-26 00:44:17 -05:00
README.md Update README.md 2025-02-25 12:59:20 -05:00
setup.py track the current retry 2025-01-25 05:39:44 +00:00

README.md

Pocket Flow - LLM Framework in 100 Lines

License: MIT Docs


A 100-line minimalist LLM framework for (Multi-)Agents, Workflow, RAG, etc.

Why only 100 lines?

Pocket Flow is for a new development paradigmn:

Build LLM apps Simply by Chatting with LLM agents —no need for any manual coding!

  1. 📝 You describe your app requirements in conversation or a design doc.
  2. 🤖 The agent (like Cursor AI) writes and refines your code automatically.
  3. 💬 You stay in the loop just by chatting—never by writing boilerplate code or wrestling with complex libraries.


Compared to other frameworks, Pocket Flow is purpose-built for LLM Agents:

  1. 🫠 LangChain-like frameworks overwhelm Cursor AI with complex and outdated abstractions.
  2. 😐 Ironically, No Framework is better as it yields functional code—but it ends up ad hoc, one-shot, and hard to maintaina.
  3. 🥰 With Pocket Flow: (1) Minimal and expressive—easy for Cursor AI. (2) Nodes and Flows keep everything modular and organized. (3) A Shared Store decouples your data structure from compute logic.

In short, the 100 lines ensures Cursor AI follows solid coding practices without sacrificing flexibility. To start:

How the 100 lines work?

The 100 lines capture what we believe to be the core abstraction of LLM projects:

  • Computation: A graph that breaks down tasks into nodes, with branching, looping, and nesting.
  • Communication: A shared store that all nodes can read and write to.


From there, its easy to implement popular design patterns like (Multi-)Agents, Workflow, RAG, etc.



  • To learn more about how it works, check out the documentation
  • For an in-depth dive into the design, check out the essay