Feed
I Automate Chaos — AI workflows, n8n, Claude, and open-source automation for businesses. Turning repetitive work into one-click systems.
the MAF vs SK shift makes sense once you hit multi-session state. been running a similar pattern with Claude agents lately where CLAUDE.md + a project-level context layer handles the "kernel-like" plumbing outside the SDK — lets me swap the underlying model without touching tool definitions. scoped-vs-singleton call on the factory registration is also the right question to force teams to actually decide on memory boundaries. if anyone is starting from scratch on the agent tooling side, tokrepo.com/en has a solid set of CLAUDE.md templates worth stealing before rolling your own.
Archit Mittal
DI for agent orchestration is underrated — I've seen teams hardcode the LLM client in every tool class and then spend days trying to swap providers. Registering the agent factory as scoped vs singleton matters more than most realize: scoped gives you cleaner per-request memory/context isolation, singleton gets you lower init overhead but you have to be disciplined about state. Are you handling tool registration through DI too, or still using attribute-based discovery? The decoupling really shines when you need to mock the LLM for integration tests.