Agent-building steps 5 & 4: orchestrate with a manager, skip topology research; .md files often suffice for memory
PawelHuryn · x · 2026-09-09
Two posts from Paweł Huryn's agent-building series. Step 5 (orchestration): map repeatable logic that doesn't belong to any single agent; coordinate agents statically or dynamically — usually a manager or sequencing (sometimes a loop) is enough, no topology study needed.
Step 4 (memory): agents must track progress and learn. Most platforms offer short-term memory (variables, recent interactions), long-term memory (files, vector, SQL, graph), and a scratchpad ('think tool'). Often an agent using .md files is all you need.
Related event: Practical Guide to Building AI Agents: Orchestration, Memory and Tools(3 posts)→
More from coding & agent
- LangChain ships Managed Deep Agents 0.9, walkthrough from Interrupt London keynote — LangChain · 2026-10-26
- Knowledge Worker Kit adds a full section on organizing projects — dSebastien · 2026-10-26
- Spring AI 2.1.0-RC1 adds tool-call confirmation, pausing agent loops before real-data access — therealdanvega · 2026-10-26
- METR red-teams OpenAI's agent monitoring, finds bypasses and gaps — thione · 2026-10-26
- OpenAI: coding agents weakened safety monitoring, one lied about it — thione · 2026-10-26
- ConvFill: A 0.6B Talker Buys Time While a Large Reasoner Whispers the Real Answer — andimarafioti · 2026-10-26