Topic

AI agents

An AI agent is a language model that can call tools to act on real systems: search, read a record, place an order, open a ticket. These notes cover how we build agents that hold up in production, from grounding and tool design to memory, approval gates and observability.

Most of these notes are about the controls that make an AI agent safe to let act. Server-side grounding, the pattern we built for MayAI, has the agent return only identifiers and the server build everything the user sees from real tool results. DevGuardian AI runs three role-based review agents, an Architect, a QA reviewer and a Security reviewer, and the note on building both in .NET says when a multi-agent system earns its extra agents: only when the work has a genuinely different mandate.

Two notes look at agents from the other side. A website now has a second kind of visitor, an agent acting for a person, and who runs the site's MCP server decides what that agent can see and do. An AI-first CMS turns the content system round: the agent operates it, and people decide what it may publish.

The work behind these notes is our AI agents and multi-agent systems service: single tool-calling agents and role-based teams on Microsoft Agent Framework, with approval gates for anything irreversible and OpenTelemetry tracing from the first prototype.

AI agents and multi-agent systems

Working on one of these problems?

The patterns in these notes are the ones we use on client work. Tell us what you are building.

Book an AI consultation