Agent-building steps 3 & 4: turn fixed procedures into tools for determinism; .md files often enough for memory
PawelHuryn · x · 2026-09-09
Paweł Huryn's agent-building series continues. Step 3 (connect tools): inventory everything the agent needs — simple tools, custom functions, integrations, CLIs, data sources, MCP servers. Key tip: turn every fixed-step procedure into a tool to make it deterministic.
Step 4 (memory): agents must track progress and learn; options include short-term memory (variables, recent interactions), long-term memory (files, vector, SQL, graph), and a scratchpad ('think tool'). In many cases an agent using .md files suffices.
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
- 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
- Tip: have your coding agent maintain a cross-linked markdown wiki under docs/ for persistent decisions — chris_j_paxton · 2026-09-09