Reflections
ChatBotKit Reflections Topics for architecture
ChatBotKit is a conversational AI platform that helps you build, train, and deploy AI-powered chatbots and virtual assistants for your business.
- Agentic Work Must Be Time-BoundA durable workflow can be paused forever, and that is exactly the footgun. The longer an agent runs, the more loops, code drift and world drift it picks up. The fix is to make agentic work strictly time-bound, so a failed attempt restarts in a clean conversation instead of dragging stale assumptions forward.
- Human in the Loop, Just Not Like ThisHuman in the loop, the way people build it today, is an approve button bolted onto a dangerous tool call. That version is broken. A human can absolutely be in the loop, just not as a rigid gate the agent can condition them to rubber-stamp.
- Every Problem Looks Like a Coding ProblemCode is flexible enough that in principle any problem becomes a coding problem. The catch is that a system's real constraints only surface after the code is written, which is why reusable components engineered from the ground up hold up where improvised code falls apart.
- Two Kinds of Enterprise AgentsTwo kinds of agents are taking shape inside companies. A personal agent that is custom to each person, and a super agent that orchestrates work across the whole business. An AI-native company runs both.
- Sub-Agents Are Not the Only WayAn orchestrator managing sub-agents became the default multi-agent pattern because coding assistants ship it, not because it is good. There is another shape, where each agent orchestrates itself and they coordinate through a shared bus.
- Agent Harnesses Are Quietly HardBuilding a useful agent is not just about the model. The harness around it has to align across context, tools, state, security, and recovery.
- Skills Are an Expensive Form of RAGSkills, MCP, and RAG all solve the same problem. Skills just do it with the worst context economics. If smaller models are the future of agents, a skills-first architecture is already a dead end.
- Pages Describe AI Agents, Blueprints Describe AI SystemsDescribing an agent in a markdown file works great until you have two of them. Single agents fit on a page. Systems of agents do not.
- When Someone Else Controls the LightsMost organisations building on AI are one provider decision away from a blackout. The electrical grid cannot arbitrarily cut your power. Your model provider can.
- The Age of Rapid PrototypingAI agent frameworks are multiplying faster than anyone can evaluate them. The winning strategy is not picking the right one - it is prototyping relentlessly until the right architecture reveals itself.
- Agents Need Supervisors Not SchedulersWe have not figured out agent orchestration yet. The next pattern is not smarter scheduling but supervision - pairing autonomous generators with autonomous verifiers.
- What It Really Takes to Build an AI AgentA comprehensive look at the hidden complexities of building production AI agents - the challenges that only become apparent through experience, covering context management, security, integrations, state, observability, and more.