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
- xbrlkit: open-source XBRL layer over Arelle with built-in MCP server support — jfrench009 · 2026-09-09
- Herdr lead agent orchestrates sub-agents with worktree and PR skills, dev ditches the GUI — iannuttall · 2026-09-09
- Session acting weird? Open a new one: practitioners' fix for momentum prior and context rot — gerardsans · 2026-09-09
- Dev Adds a Complete Tech Tree With GPT-6 Astra in 2h21m — Dimillian · 2026-09-09
- Cheap models via OpenRouter fall apart in agentic harnesses: GLM and DeepSeek can't match Claude — scottyLogJobs · 2026-09-09
- Multi-agent coding's hardest problem: deciding who is allowed to change what — apghere · 2026-09-09