Building agents with Claude in Foundry: Choosing your stack | THRSP1157

Maya Nielan explains how to choose a stack for production-grade Claude agents, drawing on lessons from building Claude Code and Cowork. The session focuses on which parts of the agent to own and which to delegate to a managed platform.

Separating the architecture decisions

The session organizes agent architecture into three choices:

Separating these decisions provides a way to compare platforms without treating the model, orchestration layer, and hosting environment as a single choice. Claude’s agent harness can be used with Microsoft Foundry; the broader decision is how much control the application needs versus how much hosting responsibility a managed service should take on.

Agent stacks and deployment options

Nielan covers Anthropic’s Messages API, Claude Agent SDK, and Claude Managed Agents, alongside Microsoft Agent Framework, Foundry Agent Service, and Copilot Studio.

The comparison centers on control versus managed hosting. It considers harness and deployment options together, with examples spanning education, insurance, engineering, and enterprise use cases.

The session also addresses the transition from prototypes to production, including:

Keeping tools portable

MCP and skills are presented as ways to keep tools portable across agent stacks. This portability is part of the stack-selection discussion: prompts, tools, and system integrations matter alongside the choice of model, harness, and hosting platform.

Session chapters

Resource