LEARNING NOTES · Outside the Buku Pi

Written Outside Buku Pi

Here I keep my personal reflections, my learning process, and how my assessments have changed. Many of these assessments come from a single real practice; after reading source code or articles, I often go back and correct my earlier understanding. These notes will not be rewritten into an overly tidy path to success, and they do not carry the responsibility of being a Buku Pi tutorial.

The following quote is the original text I wrote when I decided to put together the Buku Pi.

2026-09-08 18:48:38 · Original text

I am getting ready to tidy up my own Pi learning process

I do not know how many people will see it, but sharing is a meaningful thing; tidying it up myself is also a form of reflection on the learning process

Over the past two months, from a simple Pi Agent to studying the source code, analyzing what is inside, learning and growing step by step until I started writing my own plugins

At first it was pure curiosity: why is there an Agent this simple, and why did Openclaw choose it as the foundation for development. Slowly I came to understand the reason

I strongly suggest that, in between learning sessions, you look at the author's history. It is not just a look back at history, but an encounter with ideas, and it also answers why all of this happened

I have talked enough, let us get to work. If you are interested too, let me know in the comments👇

A Chain of Translations: From Sessions to Context

After reading three translations — session portability, context compaction, and prompt cache — I connected them into a single question: when you switch models or switch Agents, how many work records can still be inspected and changed?

Read "Why Pi Puts Sessions and Context in Your Hands"

From a Timeline to a Learning Route

98 original texts have been tidied into six stages. The order of the stages serves the learning process, while within each stage the chronological order of publication is preserved. That way, beginners know what to read first, without erasing the order in which I understood things at the time.

STAGE 01 · 27 original textsGetting to know Pi out of curiosityFirst understand what Pi is, why it stays simple, and how the Agent Harness affects the real experience.STAGE 02 · 25 original textsFinish your first task firstLearn about model selection, beginner tips, and the basic interface, then return to a small task you can verify on your own.STAGE 03 · 7 original textsUnderstanding Sessions and contextUnderstand the relationship between the session tree, long-term memory, compaction, tokens, and prompt cache.STAGE 04 · 22 original textsBuilding your own Skills and ExtensionsMove from using ready-made plugins to tidying up your methods, controlling the number, and then solving your own real needs.STAGE 05 · 7 original textsGetting sub-Agents to share the rolesLearn how to split search, tidying, and review tasks, and how to check the evidence each Agent returns.STAGE 06 · 10 original textsTurning Pi into a long-term workflowHandle VPS, remote devices, Runtime, interfaces, and the ecosystem, so that Pi moves from a one-off task to long-term use.

What I Want to Keep

Learning notes will keep the assessments I made at the time as well as later corrections. Some of the early tweets depend on the version at the time, and the language has not been polished again. Everything is kept because the learning process itself includes trial and error.

Content that readers really need to follow will go into the Buku Pi's main path, with re-verification of commands, versions, and verification results. The personal notes explain how I got here; the two parts are connected, but they carry different jobs.

Start reading from the first stage · See all six stages

If you want to know who put this route together, you can read About the author.