Memory Architecture for Long-Running AgentsMost agent frameworks treat memory as a solved problem: embed everything, retrieve the top-k chunks, stuff them into the prompt. This works fine for a chatbot that lives for one session. It falls aparJul 10 · 7 min readhumux.hashnode.dev
Skills Over Code: Teaching Agents via MarkdownEvery agent framework I’ve used has the same onboarding story: you want the agent to check the weather, so you write a WeatherTool class. You define the input schema. You write the API call. You regisJul 10 · 7 min readhumux.hashnode.dev
Running a Full Agent Stack in a Single ContainerThe conventional wisdom is that each concern gets its own service. Web server, database, task queue, model inference — four containers minimum, plus orchestration to keep them talking. For a personal Jul 9 · 6 min readhumux.hashnode.dev
Designing Multi-Channel Agent ArchitecturesHow to build agents that operate across Telegram, email, calendar, and CLI as a unified system. The moment you connect an agent to a second communication channel, you face a design fork. Either you wrJul 7 · 6 min readhumux.hashnode.dev
